Open sxa opened 4 months ago
JDK8 result:
Stack trace: Execution failed:
main' threw exception: java.security.ProviderException: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_ARGUMENTS_BAD`
Also fails in the same way on Debian12: https://ci.adoptium.net/job/Grinder/10528/consoleFull
Series of tests with a CUSTOM_TARGET of sun/nio/cs/TestCharsetMapping.java sun/nio/cs/TestIBMBugs.java sun/nio/cs/TestCharsetMapping.java sun/nio/cs/TestIBMBugs.java sun/security/pkcs11/ec/TestCurves.java sun/security/pkcs11/Provider/Login.sh sun/security/pkcs11/Secmod/AddPrivateKey.java sun/security/pkcs11/Secmod/GetPrivateKey.java sun/security/pkcs11/Secmod/JksSetPrivateKey.java sun/security/pkcs11/Secmod/LoadKeystore.java sun/security/pkcs11/Secmod/TrustAnchors.java sun/security/tools/keytool/autotest.sh sun/security/pkcs11/ec/TestCurves.java sun/security/pkcs11/Provider/Login.sh sun/security/pkcs11/Secmod/AddPrivateKey.java sun/security/pkcs11/Secmod/GetPrivateKey.java sun/security/pkcs11/Secmod/JksSetPrivateKey.java sun/security/pkcs11/Secmod/LoadKeystore.java sun/security/pkcs11/Secmod/TrustAnchors.java sun/security/tools/keytool/autotest.sh sun/security/pkcs11/fips/TestTLS12.java
to cover the issues linked in the titles of this table
Grinder | machine | sun/nio/cs | pkcs11 | TestTLS12 | autotest |
---|---|---|---|---|---|
10530 | Ubu24.04 (P) | ✅ | ✅ | ❌ | ✅ |
10531 | AL2023 | ✅ | ❌ | ✅ | ❌ |
10532 | Debian12 | ✅ | ✅ | ❌ | ✅ |
10533 | UBI9 | ✅ | ❌ | ✅ | ❌ |
10534 | UBI8 | ✅ | ✅ | ❌ | ✅ |
10535 | Fedora39 | ✅ | ❌ | ✅ | ❌ |
10536 | AL2023 | ✅ | ❌ | ✅ | ❌ |
10537 | Ubu22.04 | ✅ | ✅ | ❌ | ✅ |
10538 | Ubu20.04 | ✅ | ✅ | ❌ | ✅ |
10540 | Ubu24.04 | ✅ | ✅ | ❌ | ✅ |
10541 | Ubu16.04 | ✅ | ✅ | ✅ | ✅ |
10542 | CentOS7 | ✅ | ✅ | ❌ | ✅ |
10543 | RHEL8 (P) | ✅ | ✅ | ❌ | ✅ |
Noting that the TestTLS12 tests were excluded for Linux/ppc64le ONLY at https://github.com/adoptium/aqa-tests/pull/4652/files As per that issue - on Linux/ppc64le they fail on a centos74 system but pass on Ubuntu 20.04 (which is not consistent with the x64 failure in the table above)
EDIT: Test on Ubuntu 20.04/ppc64le is skipped with Test skipped: TLS 1.2 mechanisms not supported by current SunPKCS11 back-end
For reference as potentially related: https://bugs.openjdk.org/browse/JDK-8029661
I've been trawling through the commit history for this test and related files on JDK 8, 11, 17, and 21.
I think it would be worth opening a JBS issue for this and asking one of the SME's in the area to help as there is a history of test failure reports and fixes in the area.
For reference:
jdk8u: https://github.com/openjdk/jdk8u/blob/master/jdk/test/sun/security/pkcs11/fips/TestTLS12.java jdk11u: https://github.com/openjdk/jdk11u/blob/master/test/jdk/sun/security/pkcs11/fips/TestTLS12.java jdk17u: https://github.com/openjdk/jdk17u/blob/master/test/jdk/sun/security/pkcs11/tls/tls12/FipsModeTLS12.java jdk21u: https://github.com/openjdk/jdk21u/blob/master/test/jdk/sun/security/pkcs11/tls/tls12/FipsModeTLS12.java jdk: https://github.com/openjdk/jdk/blob/master/test/jdk/sun/security/pkcs11/tls/tls12/FipsModeTLS12.java
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 and UBI8 although not specifically called out in the AL2023 testing: 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/5380Noting that the JDK11 test of the same name passes with
Cannot resolve artifact, please check if JIB jar is present in classpath. Test skipped: failure during initialization
`