-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8327098: GTest needs larger combination limit #18083
8327098: GTest needs larger combination limit #18083
Conversation
This reverts commit 702710e.
👋 Welcome back kdnilsen! A progress list of the required criteria for merging this PR into |
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.
It looks okay, but I have questions:
- Does it happen in mainline right now?
- Why are we hitting it with JDK-8324649 PR? I don't see new logging tags added there.
@kdnilsen 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 233 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 (@shipilev, @phohensee) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@shipilev: @earthling-amzn shares that he has seen this same failure on our Shenandoah repository and have applied a similar fix there. It may be that the new ShenandoahFreeSet introduces more combinations of log tags than had been present previously. |
Weird, I just tried to run all gtests with #17561, and it passes well without these adjustments. Puzzling. |
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.
Not clear why this is needed, so I am rescinding review for a while.
This change was made experimentally in this PR to evaluate whether this would resolve regressions in GHA tests. When present, this PR passed all GHA tests. When absent, it does not.
GHA failures are unrelated. |
Note that there is also: JDK-8325490 |
/integrate |
/sponsor |
Going to push as commit c901da4.
Your commit was automatically rebased without conflicts. |
@ysramakrishna @kdnilsen Pushed as commit c901da4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The current value of LogSelectionList::MaxSelections is too small, causing GTest failures. This increases the value from 256 to 320.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18083/head:pull/18083
$ git checkout pull/18083
Update a local copy of the PR:
$ git checkout pull/18083
$ git pull https://git.openjdk.org/jdk.git pull/18083/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18083
View PR using the GUI difftool:
$ git pr show -t 18083
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18083.diff
Webrev
Link to Webrev Comment