Skip to content
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

JDK19 Windows serviceability_jvmti_j9_0_FAILED serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java timed out #16826

Closed
JasonFengJ9 opened this issue Mar 6, 2023 · 3 comments

Comments

@JasonFengJ9
Copy link
Member

JasonFengJ9 commented Mar 6, 2023

          This test was timedout at [JDK19 x86-64_windows milestone 1 build](https://hyc-runtimes-jenkins.swg-devops.com/job/Test_openjdk19_j9_extended.openjdk_x86-64_windows/31/)(`win16x64rt-1-8`)
[2023-03-02T23:30:55.210Z] variation: Mode650
[2023-03-02T23:30:55.648Z] JVM_OPTIONS:  -XX:-UseCompressedOops 

[2023-03-03T00:06:44.109Z] TEST: serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java

[2023-03-03T00:06:44.111Z] TEST RESULT: Error. Program `C:\Users\jenkins\workspace\Test_openjdk19_j9_extended.openjdk_x86-64_windows\openjdkbinary\j2sdk-image\bin\java' timed out (timeout set to 960000ms, elapsed time including timeout handling was 1702937ms).
[2023-03-03T00:06:44.112Z] --------------------------------------------------
[2023-03-03T00:06:44.112Z] Test results: passed: 117; error: 1
[2023-03-03T00:07:09.055Z] Report written to C:\Users\jenkins\workspace\Test_openjdk19_j9_extended.openjdk_x86-64_windows\jvmtest\openjdk\report\html\report.html
[2023-03-03T00:07:09.055Z] Results written to C:\Users\jenkins\workspace\Test_openjdk19_j9_extended.openjdk_x86-64_windows\aqa-tests\TKG\output_16777989179269\serviceability_jvmti_j9_1\work
[2023-03-03T00:07:09.055Z] Error: Some tests failed or other problems occurred.
[2023-03-03T00:07:09.055Z] -----------------------------------
[2023-03-03T00:07:09.055Z] serviceability_jvmti_j9_1_FAILED

Originally posted by @JasonFengJ9 in #16756 (comment)

50x grinder - 16/50 failed w/ timed out

Grinder_iteration_2
Grinder_iteration_4
Grinder_iteration_1

19:05:49  variation: Mode650
19:05:49  JVM_OPTIONS:  -XX:-UseCompressedOops 

20:06:24  TEST: serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java

20:06:24  TEST RESULT: Error. Program `C:\Users\jenkins\workspace\Grinder_iteration_2\openjdkbinary\j2sdk-image\bin\java' timed out (timeout set to 960000ms, elapsed time including timeout handling was 1719687ms).
20:06:24  --------------------------------------------------
20:06:24  Test results: passed: 118; error: 1
20:06:31  Report written to C:\Users\jenkins\workspace\Grinder_iteration_2\jvmtest\openjdk\report\html\report.html
20:06:31  Results written to C:\Users\jenkins\workspace\Grinder_iteration_2\aqa-tests\TKG\output_16778883347317\serviceability_jvmti_j9_1_ITER_2\work
20:06:31  Error: Some tests failed or other problems occurred.
20:06:31  
20:06:31  serviceability_jvmti_j9_1_FAILED(ITER_2)
@JasonFengJ9 JasonFengJ9 changed the title JDK19 Windows serviceability_jvmti_j9_0_FAILED serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java Fatal error: check_resumed_state: expected SUSPENDED flag in thread state or timed out JDK19 Windows serviceability_jvmti_j9_0_FAILED serviceability/jvmti/vthread/BreakpointInYieldTest/BreakpointInYieldTest.java timed out Mar 6, 2023
@babsingh
Copy link
Contributor

babsingh commented Mar 8, 2023

In this issue, the reported timeout is due to a deadlock, which is addressed in #16856.

babsingh added a commit to babsingh/openj9 that referenced this issue Mar 8, 2023
The VirtualThread J9Hooks trigger callbacks which can utilize JVMTI
RawMonitors. The usage of JVMTI RawMonitors can conflict with the
J9JavaVM->liveVirtualThreadListMutex and lead to deadlocks. So, these
J9Hooks should be invoked after the liveVirtualThreadListMutex is
released to avoid deadlocks.

Related: eclipse-openj9#16826

Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
babsingh added a commit to babsingh/openj9 that referenced this issue Mar 8, 2023
The VirtualThread J9Hooks trigger callbacks which can utilize JVMTI
RawMonitors. The usage of JVMTI RawMonitors can conflict with the
J9JavaVM->liveVirtualThreadListMutex and lead to deadlocks. So, these
J9Hooks should be invoked after the liveVirtualThreadListMutex is
released to avoid deadlocks.

Related: eclipse-openj9#16826

Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
@babsingh
Copy link
Contributor

babsingh commented Mar 9, 2023

This failure should be fixed by #16857 in the JDK19 release branch. The first grinder didn't run completely due to infra issues. So, launched a second grinder, which is still running. The BreakpointInYieldTest failure was not seen in the first grinder.

@fengxue-IS fengxue-IS added this to the Java 19 0.37 milestone Mar 9, 2023
@babsingh
Copy link
Contributor

Closing. Fix: #16856 and #16857.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants