-
Notifications
You must be signed in to change notification settings - Fork 724
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 serviceability_jvmti_j9_0_FAILED check_vthread_consistency_suspended: vthread is expected to be virtual #16751
Comments
@JasonFengJ9 This failure should not block JDK19. So, I will target this issue for JDK20. In the meanwhile, we can disable the test. The failure is intermittent. There is a slow path in the test case, which isn't always taken. In the slow path, the new JVMTI extension function ( |
Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
If no virtual thread is mounted on the targetThread i.e. carrierThreadObject == threadObject, then return null for the output virtual thread value. Virtual thread is not pinned in this function. So, read threadObject and carrierThreadObject once and store their values to avoid inconsistency. Related: eclipse-openj9#16688 Related: eclipse-openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
Continuation.execute is renamed to Continuation.enter. Matching the RI will allow us to run more OpenJDK tests without tweaking them for our implementation and be better prepared to support unimplemented/new features in the future. Related: eclipse-openj9#16688 Related: eclipse-openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]>
* Set up jdk for jck interactive (#4239) * Set up jdk for jck interactive Signed-off-by: Sophia Guo <[email protected]> * Add parameter SETUP_JCK_RUN explicitely Signed-off-by: Sophia Guo <[email protected]> --------- Signed-off-by: Sophia Guo <[email protected]> * [Jtreg/FFI] Disable FFI related test suite in JDK20 (#4318) The change is to exclude the FFI related test cases in AttachTest.java captured at eclipse-openj9/openj9#16656 given the FFI related code in JDK20 has been disabled for the moment and will be enabled once the code has been updated against the latest APIs. Signed-off-by: ChengJin01 <[email protected]> * Fix if condition for tck interactive setup (#4320) Signed-off-by: Mesbah Alam <[email protected]> * [Jtreg/FFI] update the issue no for FFI test suites in JDK20 (#4324) The change updates the issue no by replacing #16656 with #16565 as #16656 will be closed as duplicate of #16565, in which case #16565 serves as the only issue that keeps track of the excluded FFI test suites in JDK20. Signed-off-by: ChengJin01 <[email protected]> * Add OpenJ9 timeout handler to security and rmi extended tests (#4333) Signed-off-by: Peter Shipton <[email protected]> * Disable GetStackTraceSuspendedStressTest (#4360) Related: eclipse-openj9/openj9#16751 Signed-off-by: Babneet Singh <[email protected]> * Update JDK20 exclude list (#4371) Re-enable Thread related tests fixed in JDK19 Signed-off-by: Jack Lu <[email protected]> * Disable ContinuationTest (#4380) ContinuationTest is being disabled for OpenJ9 since it is specific to the reference implementation and it does not apply to OpenJ9. Signed-off-by: Babneet Singh <[email protected]> * Permanently disable ContinuationTest (#4382) Refer to #1297 to permanently exclude. Related: eclipse-openj9/openj9#16792 Related: #1297 Signed-off-by: Babneet Singh <[email protected]> * Exclude jdk/internal/platform/docker/TestDockerCpuMetrics.java (#4387) Signed-off-by: Jason Feng <[email protected]> * AUTO: auto exclude test jdk_svc_sanity plat=ppc64_aix impl=hotspot (#4389) - related: #4218 (comment) Signed-off-by: GitHub <[email protected]> Co-authored-by: smlambert <[email protected]> --------- Signed-off-by: Sophia Guo <[email protected]> Signed-off-by: ChengJin01 <[email protected]> Signed-off-by: Mesbah Alam <[email protected]> Signed-off-by: Peter Shipton <[email protected]> Signed-off-by: Babneet Singh <[email protected]> Signed-off-by: Jack Lu <[email protected]> Signed-off-by: Jason Feng <[email protected]> Signed-off-by: GitHub <[email protected]> Co-authored-by: Cheng Jin <[email protected]> Co-authored-by: Mesbah Alam <[email protected]> Co-authored-by: Peter Shipton <[email protected]> Co-authored-by: Babneet Singh <[email protected]> Co-authored-by: Jack Lu <[email protected]> Co-authored-by: Jason Feng <[email protected]> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: smlambert <[email protected]>
Re-enabled JDK19/JDK29 |
Don't forget to remove the "test excluded" label. |
The fix isn't in the 0.37 branch, so we can expect the jdk19 testing on 0.37 to fail. |
Do we want this fix in |
No. See #16751 (comment). |
Failure link
From an internal build(
paix817
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
This failure occurred across platforms.
x86-64_linux
ppc64le_linux
FYI @babsingh
The text was updated successfully, but these errors were encountered: