-
Notifications
You must be signed in to change notification settings - Fork 729
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
Labels
Milestone
Comments
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
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>
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally posted by @JasonFengJ9 in #16756 (comment)
50x grinder - 16/50 failed w/
timed out
Grinder_iteration_2
Grinder_iteration_4
Grinder_iteration_1
The text was updated successfully, but these errors were encountered: