8253505: JFR: onFlush invoked out of order with a sorted event stream #116
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 41 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 41 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 4307fa6. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi,
Could I have a review of a fix that makes sure EventStream::onFlush is always called after events in a segment has been pushed.
Testing jdk/jdk/jfr
Thanks
Erik
Progress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk16 pull/116/head:pull/116
$ git checkout pull/116