-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8373642: Test vmTestbase/nsk/monitoring/GarbageCollectorMXBean/CollectionCounters/CollectionCounters003/TestDescription.java failed #28923
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
…llectionCounters/CollectionCounters003/TestDescription.java failed
|
👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into |
|
@kevinjwalls 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 75 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 |
|
@kevinjwalls The following label 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 list. If you would like to change these labels, use the /label pull request command. |
| updateCounters(); | ||
| validate(true); | ||
| } while (stresser.continueExecution()); | ||
| Algorithms.eatMemory(stresser); |
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.
Are you going to file a separate issue to use WB.fullGC()? Are there other monitoring tests that could also benefit from this?
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.
Yes, would like to integrate this one soon as it makes the test more reliable, my earlier change may have made it less reliable (it tests more aggressively, it never skips and likely does more iterations). Want to follow up with a survey of what other tests the Whitebox can be useful for, maybe not just this one.
|
Just checked a new batch of 30 runs and hit one failure where it iterates 39 times and fails in vmTestbase/nsk/monitoring/GarbageCollectorMXBean/CollectionCounters/CollectionCounters002/TestDescription.java with "collectionCount not increased: 2346 -> 2346". When 8373917 https://github.com/openjdk/jdk/pull/28876/files is integrated, the parsing of "-iterations=5" will work, which cuts down the risk of failure further. These tests are failing in CI so this change makes it better, and should go ahead. |
|
Thanks Chris and Sendao! |
|
/integrate |
|
Going to push as commit a1a75ab.
Your commit was automatically rebased without conflicts. |
|
@kevinjwalls Pushed as commit a1a75ab. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
In JDK-8370731 I made this test much too thorough. It was good to ensure some testing was always done, but fixing the existing loop within runOne() was wrong. We have an outer loop already in the run() method.
20, 30 or 137 (!) iterations is unnecessary. Eventually or occasionally an iteration does not cause a collection.
Limiting to 5 iterations.
This depends on the change in https://github.com/openjdk/jdk/pull/28876/files to use "-iterations=" consistently like (a few) other tests.
Tests that do some allocation and check for a collection can be unreliable.
This may also benefit from what is proposed in #28891
I'd like to get this change in though, as the test may fail more now than before.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28923/head:pull/28923$ git checkout pull/28923Update a local copy of the PR:
$ git checkout pull/28923$ git pull https://git.openjdk.org/jdk.git pull/28923/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28923View PR using the GUI difftool:
$ git pr show -t 28923Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28923.diff
Using Webrev
Link to Webrev Comment