-
Notifications
You must be signed in to change notification settings - Fork 37
8318053: GenShen: Control thread may ignore requests to start concurrent GC #339
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 wkemper! A progress list of the required criteria for merging this PR into |
kdnilsen
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.
Thanks for figuring this out.
|
@earthling-amzn 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 45 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 |
ysramakrishna
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.
Thanks for the extra logging!
Changes look good to me.
Can you add into the ticket the command-line that was used for inducing the errant behavior?
Also can you add into this PR how you tested to confirm that it no longer occurs after the fix?
Thanks!
|
I updated the ticket with the command we used to reproduce it. I've seen the issue on the first run and @kdnilsen has seen it usually before the 10th run. If I can get 50 runs without the issue, I'll consider it fixed. Also, the additional logging showed the |
|
/integrate |
|
Going to push as commit ccbb0d8.
Your commit was automatically rebased without conflicts. |
|
@earthling-amzn Pushed as commit ccbb0d8. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
If a request to interrupt an old cycle is accepted, but there is an allocation failure before the requested cycle begins, then the control thread may become stuck in a state where it believes it should ignore further concurrent cycle requests.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/shenandoah.git pull/339/head:pull/339$ git checkout pull/339Update a local copy of the PR:
$ git checkout pull/339$ git pull https://git.openjdk.org/shenandoah.git pull/339/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 339View PR using the GUI difftool:
$ git pr show -t 339Using diff file
Download this PR as a diff file:
https://git.openjdk.org/shenandoah/pull/339.diff
Webrev
Link to Webrev Comment