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
8289440: Remove vmTestbase/nsk/monitoring/MemoryPoolMBean/isCollectionUsageThresholdExceeded/isexceeded003 from ProblemList.txt #9325
Conversation
…nUsageThresholdExceeded/isexceeded003 from ProblemList.txt
👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into |
@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. |
@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 40 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 |
Thanks Alex! |
Thanks Leonid! |
/integrate |
Going to push as commit 00d06d4.
Your commit was automatically rebased without conflicts. |
@kevinjwalls Pushed as commit 00d06d4. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
More context in the bug, but there's no evidence that this test should still be problemlisted.
Adding enableVerbose in the test itself should still keep this trivial: seeing what actually happened in a test that was once labelled as failing is really important!
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/9325/head:pull/9325
$ git checkout pull/9325
Update a local copy of the PR:
$ git checkout pull/9325
$ git pull https://git.openjdk.org/jdk pull/9325/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 9325
View PR using the GUI difftool:
$ git pr show -t 9325
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/9325.diff