8372860: TestCodeCacheUnloadDuringConcCycle fails on ARM32

[wkia]

Increasing number of iterations in the test, to give it a chance to fill CodeCache enough to reach the required threshold to trigger CodeCache GC on Linux-aarch32.

The time of the test is increased, but it seems still reasonable. (15s --> 35s on my laptop, linux64)

I confirm that this fix makes the test passed on linux-aarch32.

---

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-8372860: TestCodeCacheUnloadDuringConcCycle fails on ARM32 (Bug - P4)

Reviewers

• Thomas Schatzl (@tschatzl - Reviewer)
• Aleksey Shipilev (@shipilev - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28742/head:pull/28742
$ git checkout pull/28742

Update a local copy of the PR:
$ git checkout pull/28742
$ git pull https://git.openjdk.org/jdk.git pull/28742/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28742

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28742.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back rmarchenko! 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]

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

8372860: TestCodeCacheUnloadDuringConcCycle fails on ARM32

Reviewed-by: tschatzl, shade

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 10 new commits pushed to the master branch:

• b46aef8: 8371871: libSharedCloseAgent.cpp crashes VS2019 and older VS2022 compiler
• 920a99f: 8370731: Tests in vmTestbase/nsk/monitoring/GarbageCollectorMXBean/CollectionCounters/ failed: OutOfMemoryError
• 74dca86: 8371718: (sc) Channels.new{Input,Output}Stream can allocate unbounded memory for a socket channel
• ... and 7 more: https://git.openjdk.org/jdk/compare/b60ac710bebf195972436da324983e61b51484ef...master

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@tschatzl, @shipilev) but any other Committer may sponsor as well.

➡️ 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).

[openjdk]

@wkia The following label will be automatically applied to this pull request:

• hotspot-gc

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.

[mlbridge]

Webrevs

• 00: Full (0af5da00)

[wkia]

/integrate

[openjdk]

@wkia
Your change (at version 0af5da0) is now ready to be sponsored by a Committer.

[tschatzl]

/sponsor

[openjdk]

Going to push as commit 6a6ff87.
Since your change was applied there have been 11 commits pushed to the master branch:

• 4b774cb: 8370489: Some compiler tests miss the @key randomness
• b46aef8: 8371871: libSharedCloseAgent.cpp crashes VS2019 and older VS2022 compiler
• 920a99f: 8370731: Tests in vmTestbase/nsk/monitoring/GarbageCollectorMXBean/CollectionCounters/ failed: OutOfMemoryError
• ... and 8 more: https://git.openjdk.org/jdk/compare/b60ac710bebf195972436da324983e61b51484ef...master

Your commit was automatically rebased without conflicts.

[openjdk]

@tschatzl @wkia Pushed as commit 6a6ff87.

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