8275329: ZGC: vmTestbase/gc/gctests/SoftReference/soft004/soft004.java fails with assert(_phases->length() <= 1000) failed: Too many recored phases?

[luchenlin]

I backport this for parity with 11.0.22-oracle.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• JDK-8275329 needs maintainer approval

Issue

• JDK-8275329: ZGC: vmTestbase/gc/gctests/SoftReference/soft004/soft004.java fails with assert(_phases->length() <= 1000) failed: Too many recored phases? (Bug - P2 - Approved)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 2275

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

Using diff file

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

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back andrewlu! A progress list of the required criteria for merging this PR into master 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 (902ad6d1)
• 00: Full (3d9d2b1e)

[openjdk]

⚠️ @luchenlin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

[openjdk]

@luchenlin This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

8275329: ZGC: vmTestbase/gc/gctests/SoftReference/soft004/soft004.java fails with assert(_phases->length() <= 1000) failed: Too many recored phases?

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[luchenlin]

/integrate

[openjdk]

@luchenlin
Your change (at version 902ad6d) is now ready to be sponsored by a Committer.

[GoeLin]

/sponsor

[openjdk]

Going to push as commit 10ddd51.
Since your change was applied there have been 2 commits pushed to the master branch:

• 45e3cbf: 8294427: Check boxes and radio buttons have rendering issues on Windows in High DPI env
• 046b213: 8268916: Tests for AffirmTrust roots

Your commit was automatically rebased without conflicts.

[openjdk]

@GoeLin @luchenlin Pushed as commit 10ddd51.

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