-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8354424: java/util/logging/LoggingDeadlock5.java fails intermittently in tier6 #24687
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
|
👋 Welcome back david-beaumont! A progress list of the required criteria for merging this PR into |
|
@david-beaumont 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 171 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. Possible candidates are the reviewers of this PR (@dfuch, @stuart-marks) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
@david-beaumont The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
dfuch
left a comment
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.
Hard to tell whether 1s would be enough. I'd be tempted to bump that up.
You should also take the test out of the problem list.
dfuch
left a comment
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.
The proposed changes look good to me.
stuart-marks
left a comment
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 reasonable. This raises the base timeout by 4x. It also includes the timeout factor adjustment, which can be quite large (8x?) in higher tiers. I think at this point we just have to expose it to more runs to see whether it still fails too frequently.
|
/integrate |
|
@david-beaumont |
|
/sponsor |
|
Going to push as commit e01e33d.
Your commit was automatically rebased without conflicts. |
|
@dfuch @david-beaumont Pushed as commit e01e33d. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Increasing timeout for deadlock detection and adjusting for the timeout factor in higher tiers.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24687/head:pull/24687$ git checkout pull/24687Update a local copy of the PR:
$ git checkout pull/24687$ git pull https://git.openjdk.org/jdk.git pull/24687/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24687View PR using the GUI difftool:
$ git pr show -t 24687Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24687.diff
Using Webrev
Link to Webrev Comment