-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
8309218: java/util/concurrent/locks/Lock/OOMEInAQS.java still times out with ZGC, Generational ZGC, and SerialGC #17313
Conversation
👋 Welcome back vklang! A progress list of the required criteria for merging this PR into |
@viktorklang-ora 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
|
Hello Viktor, the skara bot very helpfully has noted that this test has been problemlisted in a couple of files:
so this current PR which is proposing to fix that test would have to remove it from those two problem lists. |
@jaikiran Gah, you're obviously right, I've amended the problem lists and updated the copyright years there as well. |
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.
Hello Viktor, the changes look OK to me.
This test resides in tier1
, so if not already done, then I would suggest running tier1 once to be sure there are no unexpected issues and given that this is a GC reliant test then additionally running only this test in the CI, with a --test-repeat of something like 50, might also be a good way to see if there any intermittent failures.
@viktorklang-ora 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 95 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 |
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 good. Restricting to only using G1, which has not been failing, seems the best thing to do here.
Thanks.
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 effect of @requires vm.gc.G1
is that the test won't be selected when there is a test run that uses a different GC. Make sense and I agree restricting this test to one GC make sense.
@jaikiran I've had it run tier1 (though not in a repeat loop), since the changes proposed here only affects the execution of the test and not changing the test itself, I thought it just made sense to have it run on tier1 once (after running the specific test itself on M5 100 times). |
@viktorklang-ora that sounds good to me. |
/integrate |
Going to push as commit b86c3b7.
Your commit was automatically rebased without conflicts. |
@viktorklang-ora Pushed as commit b86c3b7. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
/backport jdk22u |
@viktorklang-ora the backport was successfully created on the branch backport-viktorklang-ora-b86c3b7a in my personal fork of openjdk/jdk22u. To create a pull request with this backport targeting openjdk/jdk22u: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/jdk22u:
|
As per conversation in the issue.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/17313/head:pull/17313
$ git checkout pull/17313
Update a local copy of the PR:
$ git checkout pull/17313
$ git pull https://git.openjdk.org/jdk.git pull/17313/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 17313
View PR using the GUI difftool:
$ git pr show -t 17313
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/17313.diff
Webrev
Link to Webrev Comment