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
8251843: jfr/tool/TestPrintJSON.java fails intermittently #1589
Conversation
👋 Welcome back egahlin! A progress list of the required criteria for merging this PR into |
Webrevs
|
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.
Looks good.
@egahlin This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. 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 17 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. ➡️ To integrate this PR with the above commit message to the |
/integrate |
@egahlin Since your change was applied there have been 40 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit feabdde. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The 'jfr' tool can print events in JSON and XML and the result is verified by reading the same file using the jdk.jfr.consumer API. The method RecordedEvent::getEndTime() exposes timestamps with nano-precision (java.time.Instant), while the tool sorts them according to ticks. It is believed that events with different ticks timestamp in some circumstances may get the same nano-precision timestamp. This leads to events not arriving in the same order and the test fails.
Fix is to sort events in the test by ticks as well
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/1589/head:pull/1589
$ git checkout pull/1589