JDK-8277359 : sun/security/pkcs11/* test failures with jtreg test timeout
  • Type: Bug
  • Component: security-libs
  • Affected Version: 18,21
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86_64
  • Submitted: 2021-11-17
  • Updated: 2023-08-08
  • Resolved: 2023-07-25
Related Reports
Duplicate :  
JDK-8268616 - sun/security/pkcs11/Cipher/TestCICOWithGCMAndAAD.java timed out
Duplicate :  
JDK-8307185 - pkcs11 native libraries make JNI calls into java code while holding GC lock
Description
pkcs11 test failing with test timeout typical of

test result: Error. Program `/opt/mach5/mesos/work_dir/jib-master/install/jdk-18+21-1341/linux-x64.jdk/jdk-18/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 494428ms).
Comments
[~rhalade] I filed JDK-8313209 for enhancing JibArtifactManager logging.
26-07-2023
[~djelinski] I am closing this as dup of JDK-8307185. Please link the tools bug once you have filed it or let me know if you want me to file one.
25-07-2023
I'm okay if you close this issue as a duplicate of JDK-8307185. Please open an RFE for improving JIB diagnostics and add a link from this bug to the new RFE.
23-07-2023
The issue with PKCS11 tests was fixed with JDK-8307185. JIB diagnostics could be improved, but we should probably have a dedicated ticket for that. In a successful test log you can find the following lines: ----------System.out:(7/365)---------- Beginning test run TestGCMKeyAndIvCheck... nssLibDir: /path/to/nsslib/ Running test with provider SunPKCS11-NSS (security manager disabled) ... ^^^^ when this line is printed, JIB is done downloading, and the actual test starts executing. These lines are not captured by jtreg when the test times out. That is already fixed under CODETOOLS-7903441, pending next jtreg release. [~dcubed] can we close this issue? Or at least update the summary to capture the intent of improving JIB logging.
21-07-2023
Here's a log file snippet for the TestCipherKeyWrapperTest.java sighting in jdk-21+23-1901-tier2: #section:main ----------messages:(8/307)---------- command: main TestCipherKeyWrapperTest reason: User specified action: run main/othervm TestCipherKeyWrapperTest started: Thu May 11 12:14:03 GMT 2023 Mode: othervm [/othervm specified] Timeout information: --- Timeout information end. finished: Thu May 11 12:22:15 GMT 2023 elapsed time (seconds): 492.262 ----------configuration:(0/0)---------- ----------System.out:(13/650)---------- Beginning test run TestCipherKeyWrapperTest... Timeout refired 480 times nssLibDir: /System/Volumes/Data/mesos/work_dir/jib-master/install/jpg/tests/jdk/nsslib/nsslib-macosx_x64/3.46/nsslib-macosx_x64-3.46.zip/nsslib/ Running test with provider SunPKCS11-NSS (security manager disabled) ... Skip, due to no support: AESWrap Skip, due to no support: AESWrap_128 Skip, due to no support: AESWrap_192 Skip, due to no support: AESWrap_256 Skip, due to no support: AESWrapPad Skip, due to no support: AESWrapPad_128 Skip, due to no support: AESWrapPad_192 Skip, due to no support: AESWrapPad_256 Completed test with provider SunPKCS11-NSS (2 ms). ----------System.err:(1/15)---------- STATUS:Passed. ----------rerun:(35/8554)*---------- <snip> result: Error. Program `/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-21+23-1901/macosx-x64.jdk/jdk-21.jdk/Contents/Home/bin/java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 492254ms). This test, just like the other three failures, PASSED while the timeout handler was running. The root cause is believed to be an on-going issue with artifactory. However, that's not why I reopened this bug. This bug should be used to add diagnostic information to the test run for the use of JibArtifactManager for resolving the NSS artifact. Capture a before time value and an after time value and report that delta on the test's stdout. For cases where JibArtifactManager eventually gets the job done, we'll have some indication that the slowness of the test is due to JibArtifactManager and not the test itself. Of course, if JibArtifactManager times out, then we should make sure that is reported clearly.
11-05-2023
Closing it for now based on Siba's analysis. Please re-open if failure is seen again.
10-02-2022