JDK22 0.46.1 serviceability_jvmti_j9_1_FAILED serviceability/jvmti/vthread/VThreadTLSTest/VThreadTLSTest.java#id1 timed out

[JasonFengJ9]

Failure link

From an internal build(win11x86-svl-rt4-1):

openjdk version "22.0.2" 2024-07-16
IBM Semeru Runtime Open Edition 22.0.2.1-rc1 (build 22.0.2+9)
Eclipse OpenJ9 VM 22.0.2.1-rc1 (build v0.46.1-release-4760d5d320, JRE 22 Windows 11 amd64-64-Bit Compressed References 20240716_33 (JIT enabled, AOT enabled)
OpenJ9   - 4760d5d320
OMR      - 840a9adba
JCL      - e0ddd8cb412 based on jdk-22.0.2+9)

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

Optional info

Failure output (captured from console output)

[2024-09-06T22:08:01.945Z] variation: Mode650
[2024-09-06T22:08:02.547Z] JVM_OPTIONS:  -XX:-UseCompressedOops -Xverbosegclog 

[2024-09-06T23:09:12.424Z] TEST: serviceability/jvmti/vthread/VThreadTLSTest/VThreadTLSTest.java#id1

[2024-09-06T23:09:12.426Z] TEST RESULT: Error. Program `C:\Users\jenkins\workspace\Test_openjdk22_j9_extended.openjdk_x86-64_windows_testList_3\jdkbinary\j2sdk-image\bin\java' timed out: timeout handler did not complete within its own timeout. (timeout set to 960000ms, elapsed time including timeout handling was 1450873ms).
[2024-09-06T23:09:12.426Z] --------------------------------------------------
[2024-09-06T23:09:12.426Z] Test results: passed: 158; error: 1
[2024-09-06T23:09:56.008Z] Report written to C:\Users\jenkins\workspace\Test_openjdk22_j9_extended.openjdk_x86-64_windows_testList_3\jvmtest\openjdk\report\html\report.html
[2024-09-06T23:09:56.008Z] Results written to C:\Users\jenkins\workspace\Test_openjdk22_j9_extended.openjdk_x86-64_windows_testList_3\aqa-tests\TKG\output_17256571232067\serviceability_jvmti_j9_1\work
[2024-09-06T23:09:56.008Z] Error: Some tests failed or other problems occurred.
[2024-09-06T23:09:56.008Z] -----------------------------------
[2024-09-06T23:09:56.008Z] serviceability_jvmti_j9_1_FAILED

50x internal grinder - 8/50 failed

[tajila]

@babsingh Please take a look

[babsingh]

The test is functioning as expected and does not present an issue that would block the 0.48 release. Therefore, it has been deferred to the 0.49 release.

The issue appears to be machine-specific, occurring primarily on slower Windows systems where the test exceeds the timeout limit, resulting in failure.

For example:

• On a faster Windows 11 machine, the test takes approximately 3 minutes to complete: link to test result
• On a slower Windows 10 machine, the same test takes between 13-15 minutes: link to test result, occasionally exceeding the 16-minute timeout limit.

Based on my findings, the test tends to run slower on older Windows versions, such as Windows 10.

To prevent these timeout issues, collaboration between the test and infrastructure teams could ensure that this test is not executed on slower machines. The other approach could be to increase the timeout limit for the test. fyi @llxia @AdamBrousseau

[llxia]

I can see that both Windows machines have 4CPU 8GB RAM 250GB Disk. @AdamBrousseau any idea what is the difference other than OS Version?