-
Notifications
You must be signed in to change notification settings - Fork 728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jdk_security1_1_FAILED SunCertPathBuilderException & CertPathValidatorException #16312
Comments
Pls try a Temurin build to compare. |
JDK 8 internal build - paix826
JDK11 internal build - rhel7lert-1-10 |
JDK8 internal build(
|
Same failure on ub22 aarch with JDK8 0.36:
|
Internal build - mac11x64rt10
Created a new issue #18875 for this. |
This error on its surface appears to be failing due to a certificate expiration. The error thrown in the CertificateValidity class indicates an expiration date of |
@jasonkatonica atm I'm only concerned about the latest failure #16312 (comment), maybe I should have created a new issue for it. It seems to be failing across the board today, I think something expired in this test in the last few hours. I will exclude it. |
I've created a new issue #18875 |
openjdk21_j9_extended.openjdk_ppc64_aix(
openjdk21_j9_extended.openjdk_aarch64_mac openjdk21_j9_extended.openjdk_aarch64_linux openjdk17_j9_extended.openjdk_aarch64_linux This occurred across Java level & platforms. |
I just promoted new jdk17 and 21 levels earlier today, possibly this is just a mismatch between the code and the tests, depending when they ran. |
openjdk21_j9_extended.openjdk_aarch64_mac
|
The test fails to build the certificate chain from the hardcoded The test was recently updated with this commit. After reverting this commit and running with the I'm further investigating to see what this commit changed, but it looks like a test rather than an underlying code problem. |
Presumably the test still passes on an Adoptium build? |
Actually it still fails on the nightly Adoptium build: https://hyc-runtimes-jenkins.swg-devops.com/view/Test_grinder/job/Grinder/45005/ |
Could it have something to do with the fact that the |
I rerun the test as is (without reverting latest change) for different builds and here's what I got:
|
Yup. So we should either exclude the test, or maybe update it work with the Mozilla certificates (in addition to OpenJDK certificates), if we think the test is of sufficient value and could possibly expose a Semeru problem in the future. |
By the way, the test has changed name. It was It was reported again here: #15106 And you excluded it back then with: adoptium/aqa-tests#3701 |
Ok, I'll create an exclude for it then. |
The test doesn't work with the Mozilla certificates. Issue eclipse-openj9/openj9#16312 The test was renamed and this is related to adoptium#3701 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Created adoptium/aqa-tests#5758 |
The test doesn't work with the Mozilla certificates. Issue eclipse-openj9/openj9#16312 The test was renamed and this is related to #3701 Signed-off-by: Peter Shipton <Peter_Shipton@ca.ibm.com>
Failure link
From an internal build(
macaarch64rt8
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
The text was updated successfully, but these errors were encountered: