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

These tests pass for me on tip. 

% uname -r
5.10.216-182.855.amzn2int.aarch64
% make exploded-test TEST="gc/shenandoah/TestAllocObjectArrays.java gc/shenandoah/TestAllocIntArrays.java" CONF=release
...
==============================
Test summary
==============================
   TEST                                              TOTAL  PASS  FAIL ERROR   
   jtreg:test/hotspot/jtreg/gc/shenandoah/TestAllocObjectArrays.java
                                                         8     8     0     0   
   jtreg:test/hotspot/jtreg/gc/shenandoah/TestAllocIntArrays.java
                                                         8     8     0     0   
==============================
TEST SUCCESS


They also pass in the GHA actions for the [shenandoah repository](https://github.com/openjdk/shenandoah). They also pass in our internal nightly testing environments. How are you running the tests? Are you using a `fastdebug` build or `release` build?

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

PR Comment: https://git.openjdk.org/jdk/pull/19322#issuecomment-2123558132