-
Notifications
You must be signed in to change notification settings - Fork 707
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
JVMTI VThreadMonitorTest fails with an unexpected monitor #16685
Comments
@thallium can you take a look at this |
In libVThreadMonitorTest.cpp:97 we are expecting the contended monitor to be either |
The test also failed for platform thread. We should check the way of triggering contention to see if this is against the spec. |
Fixes eclipse-openj9#16685 Signed-off-by: Gengchen Tuo <gengchen.tuo@ibm.com>
Currently in our code the JVMTI Monitor Contended Enter is triggered before setting the thread flag. When the JVMTI event is triggered, the contended monitor check is then triggered, but at that time we haven't set the flag so we couldn't get the correct monitor object. I've proposed a fix #16844 to set the flag before triggering the event. |
@thallium Two more tasks before we can close this issue:
|
Fixes eclipse-openj9#16685 Signed-off-by: Gengchen Tuo <gengchen.tuo@ibm.com>
Fixes eclipse-openj9#16685 Signed-off-by: Gengchen Tuo <gengchen.tuo@ibm.com>
Done, see #16895 and adoptium/aqa-tests#4420 |
@thallium Thanks. Closing as per #16685 (comment). |
Issue
The JVMTI
VThreadMonitorTest
fails with an unexpected monitor fromGetCurrentContendedMonitor
for a virtual thread.Test CMD
Test Output:
The text was updated successfully, but these errors were encountered: