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
8270961: [TESTBUG] Move GotWrongOOMEException into vm.share.gc package #4844
Conversation
|
Webrevs
|
/label hotspot-gc |
@lmesnik |
/label add hotspot-gc |
@lmesnik The |
* Usually this means that we got OOME:heap while trying to gain OOME:metaspace. | ||
* We pass test in this case as this breaks test logic. We have dedicated test configurations | ||
* for OOME:heap provoking class unloading, that why we are not missing test coverage here. | ||
*/ |
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.
This comment is unnecessary, as it adds nothing over the log message that follows.
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! I just moved it and missed that is the same as the log message.
* Usually this means that we got OOME:heap while trying to gain OOME:metaspace. | ||
* We pass test in this case as this breaks test logic. We have dedicated test configurations | ||
* for OOME:heap provoking class unloading, that why we are not missing test coverage here. | ||
* This class is used to differ OOME in metaspace and heap when trigger class unloading. |
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.
That doesn't scan so well. Perhaps something like
"This class is used to distinguish between OOME in metaspace and OOME in heap when triggering class unloading."
@lmesnik This change now passes all automated pre-integration checks. 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 22 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.
|
/integrate |
Going to push as commit 258f188.
Your commit was automatically rebased without conflicts. |
The small refactoring which consolidates shared code in the shared library. Make project more IDE-friendly.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4844/head:pull/4844
$ git checkout pull/4844
Update a local copy of the PR:
$ git checkout pull/4844
$ git pull https://git.openjdk.java.net/jdk pull/4844/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4844
View PR using the GUI difftool:
$ git pr show -t 4844
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4844.diff