RFR: 8332596: Shenandoah: problemlist TestAllocIntArrays.java#[iu-]aggressive and TestAllocObjectArrays.java#[iu-]aggressive

[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.
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

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

Commit messages:
 - 8332596: Shenandoah: problemlist TestAllocIntArrays.java#aggressive and TestAllocObjectArrays.java#aggressive

Changes: https://git.openjdk.org/jdk/pull/19322/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=19322&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8332596
  Stats: 4 lines in 1 file changed: 4 ins; 0 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