Open JasonFengJ9 opened 9 months ago
Maybe related to https://github.com/eclipse-openj9/openj9/issues/17871
8 failures, but only 1 of this test
in https://hyc-runtimes-jenkins.swg-devops.com/job/Grinder_iteration_0/3530 on ubu20le-rtp-rt3-1 with Incorrect frame count
Created https://github.com/eclipse-openj9/openj9/issues/18738 for the serviceability/jvmti/stress/StackTrace/Suspended/GetStackTraceSuspendedStressTest .java failure.
JDK21 aarch64_linux(rhel9-aarch64-3
)
[2024-04-04T02:18:55.852Z] variation: Mode150
[2024-04-04T02:18:55.852Z] JVM_OPTIONS: -XX:+UseCompressedOops -Xverbosegclog
[2024-04-04T02:20:55.278Z] TEST: serviceability/jvmti/stress/StackTrace/NotSuspended/GetStackTraceNotSuspendedStressTest.java
[2024-04-04T02:20:55.278Z] STDERR:
[2024-04-04T02:20:55.278Z]
[2024-04-04T02:20:55.278Z] Fatal error: Incorrect frame count
[2024-04-04T02:23:24.832Z] serviceability_jvmti_j9_0_FAILED
This failure is also seen with the RI: https://bugs.openjdk.org/browse/JDK-8315980. The failure is highly intermittent and it shouldn't block the 0.46 release. The source of the issue is the RI's Virtual Thread code that OpenJ9 reuses. RI has targeted JDK24 to fix this issue. Moving forward to the 0.48 release and keeping the issue open until it is fixed in the upstream by the RI.
re https://github.com/eclipse-openj9/openj9/issues/18730#issuecomment-2142864348: The failure is still highly intermittent and it also happens with the RI. This issue is not needed for the 0.48 release. The fix for the test will be delivered by the RI. The RI has targeted to fix the test in Java 24. Moving it to the Java 24 milestone to the match the RI.
Failure link
From an internal build(
ubu20le-svl-rt7-1
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
50x internal grinder - 1 failure reproduced, 4 timeout failures, and 3 failures as https://github.com/eclipse-openj9/openj9/issues/18738