openJcePlusTests_0 AssertionFailedError: Test failed: ibm.jceplus.junit.openjceplusfips.multithread.TestAES_256 timeout

[JasonFengJ9]

Failure link

From internal Test_openjdk17_j9_extended.functional_x86-64_linux_testList_0 (ubu22x86-svl-rt4-1)

java version "17.0.15" 2025-04-15
IBM Semeru Runtime Certified Edition 17.0.15.0-rc1 (build 17.0.15+6)
Eclipse OpenJ9 VM 17.0.15.0-rc1 (build v0.51.0-release-31cf5538b0, JRE 17 Linux amd64-64-Bit Compressed References 20250415_957 (JIT enabled, AOT enabled)
OpenJ9   - 31cf5538b0
OMR      - 9bcff94a2
JCL      - 6af0863c3b3 based on jdk-17.0.15+6)

Rerun in Grinder - Change TARGET to run only the failed test targets

Optional info

Failure output (captured from console output)

[2025-05-01T12:40:42.757Z] variation: NoOptions
[2025-05-01T12:40:42.757Z] JVM_OPTIONS:  

[2025-05-01T17:35:37.245Z] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12015 s <<< FAILURE! -- in ibm.jceplus.junit.TestMultithreadFIPS
[2025-05-01T17:35:37.245Z] [ERROR] ibm.jceplus.junit.TestMultithreadFIPS.testMultithreadFIPS -- Time elapsed: 12015 s <<< FAILURE!
[2025-05-01T17:35:37.245Z] org.opentest4j.AssertionFailedError: Test failed: ibm.jceplus.junit.openjceplusfips.multithread.TestAES_256 timeout! More than 4500 seconds ==> expected: <true> but was: <false>
[2025-05-01T17:35:37.245Z] 	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
[2025-05-01T17:35:37.245Z] 	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
[2025-05-01T17:35:37.245Z] 	at org.junit.jupiter.api.AssertTrue.failNotTrue(AssertTrue.java:63)
[2025-05-01T17:35:37.245Z] 	at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:36)
[2025-05-01T17:35:37.245Z] 	at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:214)
[2025-05-01T17:35:37.245Z] 	at ibm.jceplus.junit.TestMultithreadFIPS.assertConcurrent(TestMultithreadFIPS.java:117)
[2025-05-01T17:35:37.245Z] 	at ibm.jceplus.junit.TestMultithreadFIPS.testMultithreadFIPS(TestMultithreadFIPS.java:165)
[2025-05-01T17:35:37.245Z] 	at java.base/java.lang.reflect.Method.invoke(Method.java:575)
[2025-05-01T17:35:37.245Z] 	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
[2025-05-01T17:35:37.245Z] 	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
[2025-05-01T17:35:37.245Z] 
[2025-05-01T17:35:37.245Z] [INFO] 
[2025-05-01T17:35:37.245Z] [INFO] Results:
[2025-05-01T17:35:37.246Z] [INFO] 
[2025-05-01T17:35:37.246Z] [ERROR] Failures: 
[2025-05-01T17:35:37.246Z] [ERROR]   TestMultithreadFIPS.testMultithreadFIPS:165->assertConcurrent:117 Test failed: ibm.jceplus.junit.openjceplusfips.multithread.TestAES_256 timeout! More than 4500 seconds ==> expected: <true> but was: <false>
[2025-05-01T17:35:37.246Z] [INFO] 
[2025-05-01T17:35:37.246Z] [ERROR] Tests run: 2495, Failures: 1, Errors: 0, Skipped: 0

[2025-05-01T17:35:37.246Z] openJcePlusTests_0_FAILED

50x internal Grinder - repeated once in https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_iteration_1/5360

[jasonkatonica]

This is believed to be a test issue that occasionally times out in FIPS. This is a long standing known problem which we dont plan to address in the .53 release.

[jasonkatonica]

We will need to do additional work here to ensure that a proper timeout is set here. It is not exactly clear if we are seeing a rare hang here in these multi-threaded tests or we need to bump the timeout to a higher value.

[jasonkatonica]

We have not seen this timeout for a long period of time and numerous different upates have been made to the AES classes. I will close this issue for now.