8306774: Make runtime/Monitor/GuaranteedAsyncDeflationIntervalTest.java more reliable

[shipilev]

Backport the test reliability fix. The backport was not clean, because there was a conflict in ProblemList that took the test away from it. I saw no point in backporting the unclean addition to the problem-list, so this PR just omits any changes to a problemlist.

Additional testing:

• macos-aarch64-server-fastdebug, runtime/Monitor
• Linux x86_64 fastdebug, tier1 tier2 tier3 (tested implicitly with 8306774: Make runtime/Monitor/GuaranteedAsyncDeflationIntervalTest.java more reliable #1317)
• Linux AArch64 fastdebug, tier1 tier2 tier3 (tested implicitly with 8306774: Make runtime/Monitor/GuaranteedAsyncDeflationIntervalTest.java more reliable #1317)

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8306774: Make runtime/Monitor/GuaranteedAsyncDeflationIntervalTest.java more reliable

Reviewers

• Sergey Bylokhov (@mrserb - Reviewer) ⚠️ Review applies to ab8e12be
• Volker Simonis (@simonis - Reviewer) ⚠️ Review applies to ab8e12be

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/1317/head:pull/1317
$ git checkout pull/1317

Update a local copy of the PR:
$ git checkout pull/1317
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/1317/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1317

View PR using the GUI difftool:
$ git pr show -t 1317

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/1317.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back shade! A progress list of the required criteria for merging this PR into pr/1316 will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 01: Full - Incremental (3a313f68)
• 00: Full (ab8e12be)

[simonis]

Looks good to me.

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout JDK-8306774-gadi-test-reliability
git fetch https://git.openjdk.org/jdk17u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@shipilev 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:

8306774: Make runtime/Monitor/GuaranteedAsyncDeflationIntervalTest.java more reliable

Reviewed-by: serb, simonis

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[shipilev]

Push approval is here. Reviews are in. GHA is green.

/integrate

[openjdk]

Going to push as commit 58c9f6a.

[openjdk]

@shipilev Pushed as commit 58c9f6a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.