-
Notifications
You must be signed in to change notification settings - Fork 145
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
8282947: JFR: Dump on shutdown live-locks in some conditions #234
Conversation
Reviewed-by: mgronlun
👋 Welcome back jvanek! A progress list of the required criteria for merging this PR into |
Webrevs
|
Please change the PR title to "Backport 63eb0b7e8606dd9cd145e92eeeb744ff5b7be569". |
This backport pull request has now been updated with issue from the original commit. |
Actually, the lib should be
? |
Hmm. The test fails. I need to elaborate. https://github.com/judovana/jdk-tester/actions/runs/3959120089/jobs/6785321268 |
Hello! I had adapted the test. It sitll represents issue - fails on non patched jdk, and now correctly passes on patched jdk. Automated test is now running for both jfr group and jdk group. So far so good. |
it do not affect tests behavior
The pass can be visible on https://github.com/judovana/jdk-tester/actions/runs/3988734842/jobs/6840282234#step:12:187 What now? |
See |
Thank you:) Label added. All testing on my end done. Waiting for review. |
I have tried to run jdk_jfr group on master, 3 failures are not regressions (fail both with and without changes): Failures are:
|
On my local machine only the |
Interesting, so these 2 seem environment/test machine speed sensitive |
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.
Lgtm.
@judovana 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 4 new commits pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
This comment was marked as off-topic.
This comment was marked as off-topic.
@judovana Please only integrate once you have approval via |
@judovana, you must add the jdk8u-fix-request label to the JBS issue, as well as a "Fix Request (8u)" comment detailing the testing and risk associated with the backport. |
The jdk8u-fix-request somehow disapeard. Readded. The "Fix Request (8u)" is already there - https://bugs.openjdk.org/browse/JDK-8282947?focusedCommentId=14554615&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14554615 |
/sponsor |
Going to push as commit ec53e00.
Your commit was automatically rebased without conflicts. |
@phohensee @judovana Pushed as commit ec53e00. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Reviewed-by: mgronlun
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/234/head:pull/234
$ git checkout pull/234
Update a local copy of the PR:
$ git checkout pull/234
$ git pull https://git.openjdk.org/jdk8u-dev pull/234/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 234
View PR using the GUI difftool:
$ git pr show -t 234
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/234.diff