adoptium / adoptium/infrastructure
JDK8 Test failures on test-docker-alpine320-x64-2 and -3 but not -4
- Dominant language
- Python
- Stars
- 96
- Forks
- 106
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
In the october release we saw test failures appear on test-docker-alpine320-x64-2 and -3 but not -4.
JDK8 triage https://github.com/adoptium/aqa-tests/issues/6689#issuecomment-3442690729
The mauve system failures were [solved](https://github.com/adoptium/infrastructure/issues/4123) by clearing the `externalDependency` cache directory. However the following failures persist:
**Sanity openjdk**
```
java/util/ResourceBundle/Control/StressTest.java
java/util/concurrent/forkjoin/Integrate.java
java/util/concurrent/forkjoin/NQueensCS.java
```
**sanity system**
```
ParallelStreamsLoadTest_HS_0
ParallelStreamsLoadTest_HS_1
```
There were various failures from **extended openjdk**. I'm rerunning them on [-2](https://ci.adoptium.net/job/Grinder/15406/console) and [-3](https://ci.adoptium.net/job/Grinder/15407/console)
Contributor guide
Research direction
Start with the linked JDK8 triage comment and compare the Grinder runs 15406 and 15407 for test-docker-alpine320-x64-2 and -3 against -4. Review the listed sanity and extended OpenJDK failures, including the ParallelStreamsLoadTest failures. Done means identifying why the failures persist and documenting or applying the appropriate infrastructure resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- ci-cd, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100