RFR: 8332596: Shenandoah: Make TestAllocIntArrays.java#[iu-]aggressive and TestAllocObjectArrays.java#[iu-]aggressive more robustness [v3]

[SendaoYan]

> Hi all,
> The OOM failure seems a JVM bug, not a test bug. Testcase run OOM on Neoverse-N1 and Neoverse-N2, run pass on Kunpeng-920. It seems that, if the cpu work quickly, there testcases failed; if the cpu work slowly, there testcases passed.
> Before the OOM was investigated, should we problemlist these testcases. Only change the Problemlist, the risk is low.
> There 4 testcase run OOM:
> gc/shenandoah/TestAllocObjectArrays.java#aggressive
> gc/shenandoah/TestAllocObjectArrays.java#iu-aggressive
> gc/shenandoah/TestAllocIntArrays.java#aggressive
> gc/shenandoah/TestAllocIntArrays.java#iu-aggressive

SendaoYan has updated the pull request incrementally with three additional commits since the last revision:

 - Use larger ShenandoahNoProgressThreshold and/or a smaller ShenandoahCriticalFreeThreshold to avoid the OOM failures
 - Merge branch 'jbs8332596' of github.com:sendaoYan/jdk-ysd into jbs8332596
 - 8332596: Shenandoah: problemlist TestAllocIntArrays.java#aggressive and TestAllocObjectArrays.java#aggressive
   
   Signed-off-by: sendaoYan <yansendao.ysd at alibaba-inc.com>

-------------

Changes:
  - all: https://git.openjdk.org/jdk/pull/19322/files
  - new: https://git.openjdk.org/jdk/pull/19322/files/a599aeff..56f9c0e8

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=19322&range=02
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=19322&range=01-02

  Stats: 180 lines in 3 files changed: 176 ins; 4 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/19322.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/19322/head:pull/19322

PR: https://git.openjdk.org/jdk/pull/19322