-
Notifications
You must be signed in to change notification settings - Fork 10
Flaky test - j9 OSR #239
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
Flaky test - j9 OSR #239
Conversation
Skip zing and j9 flaky tests
} | ||
// Running vm stackwalker tests on JVMCI (Graal), JDK 24, aarch64 and with a sanitizer is crashing in a weird place | ||
// This looks like the sanitizer instrumentation is breaking the longjump based crash recovery :( | ||
assumeFalse(Platform.isJavaVersionAtLeast(24) && isJvmci && Platform.isAarch64() && cstack.startsWith("vm") && isSanitizer); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the usage of assume here ?
we are triggering these tests here: https://github.com/DataDog/java-profiler/actions/runs/16116032610/job/45470209849?pr=238
Is this expected ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are running on JDK 17 - one of the conditions is Java >=24
So yes. This is expected.
🔧 Report generated by pr-comment-scanbuild |
boolean isSanitizer = config.endsWith("san"); | ||
boolean isJvmci = System.getProperty("java.vm.version", "").contains("jvmci"); | ||
assumeFalse(Platform.isZing() || Platform.isJ9()); | ||
// Skip test entirely on unsupported JVMs (don't use assumeFalse which gets retried) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't use assumeFalse which gets retried
Ouch. This should not be the case. I will take a look at the @TestTemplate
engine ...
Skip zing and j9 flaky tests
* Potential memory leak with the JVMTI wallclock sampler * v1 * Don't sample terminated thread * v2 * v3 * v4 * Safe access * Fix thread state * v5 * Cleanup * Cleanup * safeFetch impl * jdk11 support * v6 * enhance and cleanup * fix nullptr deference * More cleanup * Erwan's finding * Fixed memory leak found by Erwan * [Automated] Bump dev version to 1.29.0 * Update the sonatype repos (#235) * Fix artifact download URL * Split debug (#233) * Split debug Add build steps to store split debug information for release builds * Add the micro-benchmark for thread filtering (#237) * Add the micro-benchmark for thread filtering * Do not test for obviously invalid thread id * Relax threadfilter mem order * Flaky test - j9 OSR (#239) Skip zing and j9 flaky tests * Fix flaky allocation test (#241) Lower threshold for allocation test * jbachorik's comments * More jbachorik's comments * Cleanup thread local references --------- Co-authored-by: zhengyu.gu <[email protected]> Co-authored-by: Datadog Java Profiler <[email protected]> Co-authored-by: Jaroslav Bachorik <[email protected]> Co-authored-by: Jaroslav Bachorik <[email protected]> Co-authored-by: r1viollet <[email protected]>
What does this PR do?:
Skip zing and j9 flaky tests
Motivation:
Additional Notes:
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!