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

[William Kemper]

On Tue, 21 May 2024 09:12:09 GMT, SendaoYan <syan at openjdk.org> wrote:

> 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

Okay, we have seen other tests that fail intermittently when they walk to close to the edge of memory exhaustion.

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

Marked as reviewed by wkemper (Committer).

PR Review: https://git.openjdk.org/jdk/pull/19322#pullrequestreview-2072005532