JDK8 fips/TestTLS12 failure on Ubuntu 24.04
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
Passes on the RHEL6 machine according to https://github.com/adoptium/aqa-tests/issues/5233#issuecomment-2061207176
Noted as part of the pkcs11 failures when testing [Ubuntu 24.04](https://github.com/adoptium/infrastructure/issues/3501) and [UBI8](https://github.com/adoptium/infrastructure/issues/3586) although not specifically called out in the [AL2023 testing](https://github.com/adoptium/aqa-tests/issues/5300): https://github.com/adoptium/infrastructure/issues/3614#issuecomment-2187110622
Performing new Grinder run at https://ci.adoptium.net/job/Grinder/10513 of `jdk_security3_0` to check the output before adding more details.
Related: PKCS11 test failures at https://github.com/adoptium/aqa-tests/issues/5380
Noting that the [JDK11 test of the same name](https://ci.adoptium.net/job/Grinder/10514/testReport/) passes with `Cannot resolve artifact, please check if JIB jar is present in classpath. Test skipped: failure during initialization`
`
Contributor guide
Research direction
Start by reviewing the output from Grinder/10513 for the jdk_security3_0 run and compare it with the passing RHEL6 result and the JDK11 test report. Use the related PKCS11 failure issue for context; done means identifying the Ubuntu 24.04 JDK8 TestTLS12 failure and confirming a passing test run or a documented blocker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, ubuntu
- Domain
- operating-systems, security, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100