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
8266056: runtime/stringtable/StringTableCleaningTest.java failed with "RuntimeException: Missing Callback in [10, 11]" #3815
Conversation
… "RuntimeException: Missing Callback in [10, 11]"
/cc hotspot-gc |
|
/cc hotspot-runtime |
@pliden |
@pliden |
Webrevs
|
@pliden 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 12 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.
|
Functional fix seems fine but a suggested change to the reporting.
Thanks,
David
output.outputTo(System.out); | ||
output.errorTo(System.out); |
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 normal way to do this is to call output.reportDiagnosticSummary(). But you only do that after the actual checks, when you know you have success, as in the error cases it will be called anyway and you don't want the output twice.
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.
Hmm, I see now that adding lines those is unnecessary, so I'll just remove them. Both shouldHaveExitValue() and checkOutput() seem to do the right thing. Not sure why I thought they didn't.
I had assumed you wanted to see the output even on success. :)
Update is fine.
Thanks,
David
Thanks @dholmes-ora and @coleenp for reviewing! /integrate |
@pliden Since your change was applied there have been 17 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit c5dc657. |
This patch addresses two issues with the StringTableCleaningTest test.
The test doesn't fully take into account that a concurrent GC might not complete (it can abort if the VM wants to terminate). findCallback() should return -1 if no callbacks are found, instead of failing the test.
The regexp patterns used for ZGC needs to be more exact. The end pattern now also matches aborted GCs, which it shouldn't. This leads to "Garbage Collection (*) Aborted" being incorrectly matched as a GC end.
This patch also makes sure the output from the test VM ends up in the test log, otherwise it's impossible to tell what went wrong if this test fails in the future.
This patch also removes the test from the ProblemList.
Testing:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3815/head:pull/3815
$ git checkout pull/3815
Update a local copy of the PR:
$ git checkout pull/3815
$ git pull https://git.openjdk.java.net/jdk pull/3815/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3815
View PR using the GUI difftool:
$ git pr show -t 3815
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3815.diff