-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8367026: Reorder the timeout failure handler commands to have jstack run before the rest #27574
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
Conversation
…run before the rest
👋 Welcome back jpai! A progress list of the required criteria for merging this PR into |
@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 11 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 |
/label remove core-libs |
@jaikiran |
@jaikiran |
Thank you Erik and Leonid for the reviews. |
/integrate |
Going to push as commit 17d8fa8.
Your commit was automatically rebased without conflicts. |
Can I please get a review of this change to a jtreg failure handler configured in the JDK?
The change proposes to generate a thread dump much sooner than previously whenever a test times out. This should thus capture a much more accurate state of the test process when the test is considered timed out.
Due to the recent changes in the default timeout factor, we have noticed some tests which timeout and the jtreg failure handler actions start execution. While those are being executed the test sometimes completes. So by the time the "jstack" failure handler action is executed (can be several seconds later), the test's state will no longer be accurate.
The change here generates a thread dump using jstack as the first action in the set of failure handler actions. It does it only once and then moves to the rest of the actions, one of which subsequent "jstack" which generates thread dumps more than once.
I have verified that this change works as expected when a test times out. The action is named "thread_dump" instead of just reusing the "jstack" name because the current HTML rendering of the processes.html runs into trouble if there are more than one action with the same name.
I wanted to reorder some of the other commands in that set, but it causes some trouble in the rendering of the HTML and would require some changes to that part. So I decided to keep this simple and have it done sooner to help investigating timeout failures in our CI.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27574/head:pull/27574
$ git checkout pull/27574
Update a local copy of the PR:
$ git checkout pull/27574
$ git pull https://git.openjdk.org/jdk.git pull/27574/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27574
View PR using the GUI difftool:
$ git pr show -t 27574
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27574.diff
Using Webrev
Link to Webrev Comment