-
Notifications
You must be signed in to change notification settings - Fork 721
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
JDK8 jdk_security3_0_FAILED Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: 0xCE534351 #15663
Comments
This seems like a machine problem. |
In the grinder 4 machines passed (cent7x64-1-9, ub18x64rt1-9, ub20x64rt1-4, cent7x64-1-5), one failed rhel9x86-rt1-1. The original failures were on rhel9x86-rt3-1. Maybe related to rhel9? Seem to be https://bugs.openjdk.org/browse/JDK-8282538 which is fixed in Java 11.0.17+1, 17.0.5+1, 19, i.e. the next set of releases. We have 17.0.5+1 already, but 11.0.17+1 is blocked on #15664 |
A similar internal failure (
|
We probably need to backport https://bugs.openjdk.org/browse/JDK-8282538 to jdk8. |
Seems it should already be backported via https://bugs.openjdk.org/browse/JDK-8290076, but we don't have this change as of jdk8u352-b04 |
The change is actually in jdk8u352-b01, but this is the build that failed. We should try again on the latest (b05) to see if it's still failing. sun/security/pkcs11/Cipher/CancelMultipart.java on rhel9x86-rt2-1 grinder (head) - passed |
Created #15902 for #15663 (comment), closing this one as resolved. |
JDK8 x86-64_linux 0.41 milestone 1(
|
Failing on rhel9, the grinder failed on rhel9x86-svl-rt4-1. Not an OpenJ9 issue, either JCL or machine setup. |
JDK8 ppc64le_linux(
|
@jasonkatonica fyi |
At line 486 of PKCS11Test.java, as below:
It tried to initialize the SunPKCS11 using the configure file. If the test failed during FIPS testing, that is expected, because in FIPS mode, SunPKCS11 will be initialized using the FIPS nss.fips.cfg. And it can't be initialized again in the tests. So, the Initialization failed will happen. If the test failed but not in FIPS testing, does this failure happens all the time, or failed intermittently? |
non-FIPS testing. The most recent failure is in a test run that doesn't have any TEST_FLAG set. It's likely intermittent or specific to a machine. @JasonFengJ9 pls run a grinder. |
Passed at The original error |
Failure link
From an internal build(
rhel9x86-rt3-1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
15x internal grinder - jdk_security3_0
The text was updated successfully, but these errors were encountered: