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
JDK-8277092: TestMetaspaceAllocationMT2.java#ndebug-default fails with "RuntimeException: Committed seems high: NNNN expected at most MMMM" #6451
JDK-8277092: TestMetaspaceAllocationMT2.java#ndebug-default fails with "RuntimeException: Committed seems high: NNNN expected at most MMMM" #6451
Conversation
|
…seems-high-NNNN-expected-at-most-MMMM
23642cb
to
525a285
Compare
GHA display is off; the only real test error is linux x64 hotspot compiler, but that has nothing to do with this change. |
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, I found where it calls ChunkManager::purge. This looks good. I think as a test fix, it can be integrated as "trivial".
@tstuefe 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 59 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.
|
Thank you, Coleen. The one remaining test error is unrelated (actually, compiler/c2/irTests/TestUnsignedComparison.java fails in all my GHAs currently). /integrate |
Going to push as commit a3406a1.
Your commit was automatically rebased without conflicts. |
Test error after JDK-8276731. That patch changed the way metaspace chunks are uncommitted: Before, chunks were uncommitted when being returned to the system; now they are uncommitted only if
Metaspace::purge()
is explicitly called.In real VM life, that makes no difference since these two things happen back to back in
CLDG::purge()
.But these metaspace tests isolate metaspace arenas and test them as individual units, without involving GC or CLDG, and therefore we need to purge manually. Otherwise, the commit numbers are unpredictable and may be larger than expected.
Tests: manual x64+x86, GHAs (one unrelated error in hs compiler tests on linux x64), SAP nightlies
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6451/head:pull/6451
$ git checkout pull/6451
Update a local copy of the PR:
$ git checkout pull/6451
$ git pull https://git.openjdk.java.net/jdk pull/6451/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 6451
View PR using the GUI difftool:
$ git pr show -t 6451
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6451.diff