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-8290839: jdk/jfr/event/compiler/TestJitRestart.java failed with "RuntimeException: No JIT restart event found: expected true, was false" #9612
Conversation
|
Webrevs
|
There is no guarantee that events will arrive in the recording file in the same order they were committed. If the test depends on there order(?), the events should be sorted, i.e. events.sort(Comparator.comparing(RecordedEvent::getEndTime)). |
Yes the order is important. However sorting using getEndTime leads to alot of errors, 50% of test runs fail this way (makes things worse) because we seem to have compilation events with end time later than the jdk.CodeCacheFull event. |
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 know enough about the compiler events and their order, but looks reasonable.
@MBaesken This change now passes all automated pre-integration checks. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 54 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.
|
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.
Changes look good to me.
Hi Erik and Lutz, thanks for the reviews ! |
/integrate |
Going to push as commit 5d1ad39.
Your commit was automatically rebased without conflicts. |
In seldom cases the TestJitRestart.java JFR test failed because no Jitrestart event was seen in the test.
Dean Long suggested to change the test a bit "How about changing the test to look at CodeCacheFull, compilation, and JitRestart events. It can test that no compilation events happen after CodeCacheFull unless a JitRestart comes first. So it would be testing the order of events and not absolute counts."
So I adjusted the test (still succeeds after a JitRestart is seen, but in case it is not seen only fails in case of Compilation events after CodeCacheFull).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9612/head:pull/9612
$ git checkout pull/9612
Update a local copy of the PR:
$ git checkout pull/9612
$ git pull https://git.openjdk.org/jdk pull/9612/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9612
View PR using the GUI difftool:
$ git pr show -t 9612
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9612.diff