-
Notifications
You must be signed in to change notification settings - Fork 707
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
cmdLineTester_jvmtitests_hcr_OSRG_nongold failures with JITServer on x86_64 and JDK11 #19504
Comments
Attn @mpirvu. I'll check to see if it's only the first commit of that PR, or if it needs both. |
@cjjdespres Could you please check if the test fails when we disable the disclaim with command line options: -Xjit:disableIprofilerDataDisclaiming |
The test still fails. I used |
Just to double check: this test does not fail without JITServer, correct? |
That's right, or at least a 25x grinder without JITServer had 0 failures and with JITServer it fails every time. |
These tests were failing consistently up to the May 27 nightly run. They started passing on the May 28 run and have not failed since. The difference between the May 27 and May 28 runs in openj9 is ce04759...4ff10c9. Between those commits the PR #19545 was merged, which fixed an error introduced in #19355 (that PR being the apparent cause of these failures). So, that former PR may have also fixed this issue as well. I'm still unsure how those PRs could have introduced or fixed the problem, but I think this issue can be closed in any case. |
The tests
cmdLineTester_jvmtitests_hcr_OSRG_nongold_0
andcmdLineTester_jvmtitests_hcr_OSRG_nongold_2
have started failing in the JITServer nightly tests. Both fail in thertc003
subtest, and only on X with JDK11, from what I can see. The earliest failure is this May 8 run. Console log for one of the failures in that run:A 25x grinder without JITServer did not result in any failures, and this is reproducible consistently locally with JITServer enabled.
These are the differences between failing May 8 build and the successful May 7 build:
I tested a build based on b05b2c1 and eclipse/omr@1bcf969 (so excluding bfaeffa in particular) and it did not fail, based on 3 test iterations. I tested a build based on bfaeffa and eclipse/omr@acd6f7e, and 3 test iterations both failed. So, it may be #19355 that is causing the failure, or at least causing it to appear consistently.
The text was updated successfully, but these errors were encountered: