-
Notifications
You must be signed in to change notification settings - Fork 714
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
OpenJDK serviceability/jvmti/stress/StackTrace/Suspended/GetStackTraceSuspendedStressTest #18738
Comments
JDK21 ppc64_aix(
50x grinder 2/50 failed |
serviceability/jvmti/stress/StackTrace/NotSuspended/GetStackTraceNotSuspendedStressTest.java
There was also a different failure #18675 on paix827 |
JDK22 aarch64_linux(
|
JDK21 aarch64_linux(
|
JDK21 ppc64le_linux(
|
|
https://trssrtp1.fyre.ibm.com/output/test?id=668ae6bc6b34225c2bda7712 - paix825
|
This is a different test to the original issue reported. Upon code review, this could be caused by a timing gap between vthread's last unmount and setting the vthread state to The I'll draft a PR to also check the JVM's internal state on the vthread to determine if thread is alive in |
Check if the continuation is finished to determine more accurately if a virtual thread is alive. Related: eclipse-openj9#18738 (comment) Signed-off-by: Jack Lu <Jack.S.Lu@ibm.com>
Check if the continuation is finished to determine more accurately if a virtual thread is alive. Related: eclipse-openj9#18738 (comment) Signed-off-by: Jack Lu <Jack.S.Lu@ibm.com>
From the grinder run for #18730
Internal test on ubu22lert-1
serviceability_jvmti_j9_1
serviceability/jvmti/stress/StackTrace/Suspended/GetStackTraceSuspendedStressTest.java
failed 3/10 on this machine. Didn't fail on the other 4 machines in this 50x grinder.
The text was updated successfully, but these errors were encountered: