-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8355372: GenShen: Test gc/shenandoah/generational/TestOldGrowthTriggers.java fails with UseCompactObjectHeaders enabled #24888
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 |
|
@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 83 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 |
|
@earthling-amzn The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
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.
Looks fine but left some thoughts, although you probably don't want to change anything if this setting is working to induce the behavior you want to test.
A whitebox test may be better in the future rather than having to tweak test settings to induce the right behavior to trigger old growth.
| case 0: | ||
| // 50% chance of creating garbage | ||
| array[replaceIndex] = array[replaceIndex].max(array[deriveIndex]); | ||
| break; | ||
| case 1: | ||
| // 50% chance of creating garbage | ||
| array[replaceIndex] = array[replaceIndex].min(array[deriveIndex]); | ||
| break; |
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.
Could you have left this in place & reduced the heap size of the UseCompactHeaders test to half the current setting to induce the trigger?
| for (int i = 0; i < ArraySize; i++) { | ||
| int replaceIndex = r.nextInt(ArraySize); | ||
| int deriveIndex = r.nextInt(ArraySize); | ||
| switch (i & 0x3) { |
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.
...otherwise could you just do (i & 0x1) here and change cases 2 & 3 to cases 0 & 1?
|
Hi @earthling-amzn I added your PR to our build/test queue, let's see if the issues we observed go away on all platforms! |
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.
Changes look good to me.
|
@MBaesken - thank you! Please let us know how it goes. @ysramakrishna - I wanted to increase pressure specifically on the old generation. I'm not sure reducing the heap size alone would do that. As you point out, the cases in the switch statement do look a bit silly now. I'll make the change you suggested. |
Unfortunately, not so good . gc/shenandoah/generational/TestOldGrowthTriggers.java triggers now this crash/assert |
Seems we have for this already |
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.
ok
|
@MBaesken , have you had a chance to retest after PR#24940 was integrated? |
|
/integrate |
|
Going to push as commit 9e26b9f.
Your commit was automatically rebased without conflicts. |
|
@earthling-amzn Pushed as commit 9e26b9f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Did not see the issue again after this (of course this is no 'proof' that they will never come back), so I would say looks good ! |
Add a test case for
-XX:+UseCompactObjectHeaders, increase pressure on old generation. I ran the test (which includes a compact object headers case now) fifty times without failure.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24888/head:pull/24888$ git checkout pull/24888Update a local copy of the PR:
$ git checkout pull/24888$ git pull https://git.openjdk.org/jdk.git pull/24888/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24888View PR using the GUI difftool:
$ git pr show -t 24888Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24888.diff
Using Webrev
Link to Webrev Comment