adoptium / adoptium/infrastructure

JDK8 arm32 tests failed with `fatal error` on three arm32 dockers

Open
#2,687 3 comments 0 reactions 0 assignees View on GitHub
arch:arm32 docker
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

The failures have been existed for a long time and no issue tracked.
https://github.com/adoptium/aqa-tests/issues/3603#issuecomment-1113123584

https://github.com/adoptium/aqa-tests/issues/3880#issuecomment-1192922493

com/sun/net/httpserver/Test9.java.Test9
com/sun/net/httpserver/bugs/B6361557.java.B6361557
com/sun/net/httpserver/Test12.java.Test12
sun/security/ec/TestEC.java
sun/security/ssl/SSLContextImpl/MD2InTrustAnchor.java

Some tests passed with re-run, might be machine issue?
```
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xf3f03320, pid=4171464, tid=0xd14af460
#
# JRE version: OpenJDK Runtime Environment (8.0_342-b07) (build 1.8.0_342-b07)
# Java VM: OpenJDK Client VM (25.342-b07 mixed mode linux-aarch32 )
# Problematic frame:
# j sun.security.ssl.RenegoInfoExtension$CHRenegotiationInfoAbsence.absent(Lsun/security/ssl/ConnectionContext;Lsun/security/ssl/SSLHandshake$HandshakeMessage;)V+0
#
# Core dump written. Default location: /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_arm_linux_testList_0/aqa-tests/TKG/output_16584846518090/jdk_net_2/work/scratch/3/core or core.4171464
#
# An error report file with more information is saved as:
# /home/jenkins/workspace/Test_openjdk8_hs_extended.openjdk_arm_linux_testList_0/aqa-tests/TKG/output_16584846518090/jdk_net_2/work/scratch/3/hs_err_pid4171464.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues

```

Contributor guide

Open the contributing guide

Research direction

Start with the listed JDK8 tests, the SIGSEGV log, and the linked aqa-tests comments. Compare failures and reruns across the three arm32 Docker environments to determine whether the crashes share a reproducible cause. Done means the cause is documented and the affected tests pass reliably or have a clearly tracked limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, java, linux
Domain
infrastructure, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.