8308475: Make the thread dump files generated by jcmd Thread.dump_to_file jtreg failure handler action easily accessible#14071
8308475: Make the thread dump files generated by jcmd Thread.dump_to_file jtreg failure handler action easily accessible#14071jaikiran wants to merge 1 commit intoopenjdk:masterfrom
Conversation
…file jtreg failure handler action easily accessible
|
👋 Welcome back jpai! A progress list of the required criteria for merging this PR into |
|
/add label hotspot |
|
@AlanBateman Unknown command |
|
/label add hotspot |
|
@AlanBateman |
|
@lmesnik Do you have cycles to look at this? |
|
@jaikiran 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 71 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 |
|
Thank you Leonid for the review. Since this is tagged hotspot, can I please get a second Reviewer to review this please? |
|
@jaikiran I don't know why @AlanBateman tagged this as Hotspot as there are no hotspot related changes. Perhaps it was just for visibility of shared failure handler changes? But I don't think you need a Hotspot review here. |
config/mailinglist/rules/jdk.json (in the skara repo) maps changes to test/failure_handler/ to core-libs but changes to the jtreg failure handler are of wider interest. It looks like changes to the handler have previously been cc'ed to the hotspot list too. |
|
Thank you all for the help. I'll go ahead and integrate this. |
|
/integrate |
|
Going to push as commit 426ebf4.
Your commit was automatically rebased without conflicts. |

Can I please get a review of this change which proposes to improve the accessibility of the thread dump files that are generated by the
jcmd Thread.dump_to_filecommand configured in the failure handler configurations? This addresses https://bugs.openjdk.org/browse/JDK-8308475.The changes in this PR include:
GatherProcessInfoTimeoutHandlerto allow configuring asuccessArtifactsaction parameter which can be used to generate links to files that are generated by the failure handler commands.%iterCounttoken to allow ability to refer to the current iteration when the command is repeatedjcmd Thread.dump_to_fileis now configured to create the thread dumps injsonformat. Additionally, it has now been configured to create the thread dumps 6 times, just like thejstackcommand.Detailed explanation of the
successArtifactsparameter and the%iterCounttoken is provided in the JBS comment here https://bugs.openjdk.org/browse/JDK-8308475?focusedCommentId=14583072&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14583072Tests have been run locally with this change and tier1, tier2 and tier3 tests on CI system to verify this change works and doesn't cause regression.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/14071/head:pull/14071$ git checkout pull/14071Update a local copy of the PR:
$ git checkout pull/14071$ git pull https://git.openjdk.org/jdk.git pull/14071/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 14071View PR using the GUI difftool:
$ git pr show -t 14071Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/14071.diff
Webrev
Link to Webrev Comment