-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
jdk/jfr/jcmd/TestJcmdDump.java.TestJcmdDump consistently failing in jdk18+36 Release Triage #3492
Comments
Just found that the test is excluded on aarch64-linux,linux_ppc64le and linux_s390x (yet still ran during this release)
MacOS should also be added to the exclude list |
Closing as it appears to be intermittent on MacOS |
re: adoptium/adoptium#133 (comment)
If the test was excluded (via #3044), it should not have run. Since it is running and failing, looking at how it was excluded shows us that it was not excluded properly (wrong platform name used). This particular test case is NOT a very nice one to include in the AQA suite, as it appears to be very sensitive to machine resource (therefore is flaky / intermittently failing depending on which machine it lands on). We can switch the entry in the ProblemList file to generic-all and exclude on all platforms (until the test itself can be improved to be able to run on a variety of machines). Going to reopen this issue and use it as the base issue for the exclusion until we can report and get a fix upstream if its possible (rather than #2919 which is more generic). |
Check all history it shows test only failed with non-compressed. Might be worth to check if it should be enabled for non-compressed. |
Not reproduced in recent run #4352 (comment) |
This still happens intermittently. #5444. As it only happened to non-compressed #3492 (comment), https://adoptium.slack.com/archives/C5219G28G/p1731569159139549 suggests to increase the -Xmx. |
The test jdk/jfr/jcmd/TestJcmdDump.java.TestJcmdDump.java.TestJcmdDump from the extended openjdk test suite continues to fail across some platforms
MacOS https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_mac_testList_0/27/
Trss
Linux aarch64 https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_aarch64_linux/27/testReport/jdk_jfr_jcmd_TestJcmdDump/java/TestJcmdDump/
Trss https://trss.adoptium.net/output/test?id=623aa15c72761a4c5cf7c523
linux ppc64le
Trss https://trss.adoptium.net/output/test?id=623a740572761a4c5cf761e6
https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_ppc64le_linux_testList_0/27/testReport/
Linux s390x https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_s390x_linux_testList_0/25/testReport/jdk_jfr_jcmd_TestJcmdDump/java/TestJcmdDump/
Trss https://trss.adoptium.net/output/test?id=623a657772761a4c5cf73e09
The text was updated successfully, but these errors were encountered: