-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
8324983: race in CompileBroker::possibly_add_compiler_threads #17662
Conversation
👋 Welcome back never! A progress list of the required criteria for merging this PR into |
@tkrodriguez 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
|
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.
Good.
@tkrodriguez 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 36 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 |
@dholmes-ora are you planning to approve or should I go ahead and integrate? |
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.
Thanks for the update. Thumbs up on the shared changes.
Thanks for the reviews. /integrate |
Going to push as commit 1993652.
Your commit was automatically rebased without conflicts. |
@tkrodriguez Pushed as commit 1993652. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Thanks @vnkozlov for approving the backport. /backport jdk22 |
@dougxc the backport was successfully created on the branch backport-dougxc-19936526 in my personal fork of openjdk/jdk22. To create a pull request with this backport targeting openjdk/jdk22:master, just click the following link: The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:
If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk22:
|
The number of active compiler threads is decremented before the compiler thread has actually activated so possibly_add_compiler_thread might start a new thread on the existing JavaThread. This adds a check that it's really exiting before proceeding and some new guarantees that ensure threads aren't started on top running threads.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17662/head:pull/17662
$ git checkout pull/17662
Update a local copy of the PR:
$ git checkout pull/17662
$ git pull https://git.openjdk.org/jdk.git pull/17662/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17662
View PR using the GUI difftool:
$ git pr show -t 17662
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17662.diff
Webrev
Link to Webrev Comment