-
Notifications
You must be signed in to change notification settings - Fork 236
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
8305931: jdk/jfr/jcmd/TestJcmdDumpPathToGCRoots.java failed with "Expected chains but found none" #2686
Conversation
👋 Welcome back roberttoyonaga! A progress list of the required criteria for merging this PR into |
@roberttoyonaga 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 58 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. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. ➡️ To flag this PR as ready for integration with the above commit message, type |
This backport pull request has now been updated with issue from the original commit. |
|
/approval request for the clean backport of a JFR test fix for TestJcmdDumpPathToGCRoots. This only affects test code so should be a low risk. |
@roberttoyonaga |
/integrate |
@roberttoyonaga |
/integrate |
@jerboaa Only the author (@roberttoyonaga) is allowed to issue the |
/sponsor |
Going to push as commit cabaf74.
Your commit was automatically rebased without conflicts. |
@jerboaa @roberttoyonaga Pushed as commit cabaf74. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
This is a backport of openjdk/jdk@65be5e0
This change to JFR test code is needed because TestJcmdDumpPathToGCRoots transiently fails because it can't guarantee the expected objects are sampled. The change improves cleanups between checks and also adds retries.
This should help resolve some test failures for Adoptium (see adoptium/aqa-tests#2766)
Testing: the updated test/jdk/jdk/jfr/jcmd/TestJcmdDumpPathToGCRoots.java test passes.
Progress
Issue
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/2686/head:pull/2686
$ git checkout pull/2686
Update a local copy of the PR:
$ git checkout pull/2686
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/2686/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 2686
View PR using the GUI difftool:
$ git pr show -t 2686
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/2686.diff
Webrev
Link to Webrev Comment