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

[SendaoYan]

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

On the other hand, run these tests on the same machine twice, when the cpu is busy, there testcases run passed; when the cpu is idle, there testcases run failed.


yansendao at CompilerTest-aarch64-6:[jdk]> which java
~/git/jdk/build/linux-aarch64-server-release/images/jdk/bin/java
yansendao at CompilerTest-aarch64-6:[jdk]> lscpu 
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              64
On-line CPU(s) list: 0-63
Thread(s) per core:  1
Core(s) per socket:  64
Socket(s):           1
NUMA node(s):        1
Vendor ID:           ARM
Model:               0
Model name:          Neoverse-N2
Stepping:            r0p0
CPU MHz:             3000.000
CPU max MHz:         3000.0000
CPU min MHz:         3000.0000
BogoMIPS:            100.00
L1d cache:           64K
L1i cache:           64K
L2 cache:            1024K
L3 cache:            65536K
NUMA node0 CPU(s):   0-63
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs sb dcpodp sve2 sveaes svepmull svebitperm svesha3 svesm4 flagm2 frint svei8mm svebf16 i8mm bf16 dgh
yansendao at CompilerTest-aarch64-6:[jdk]> top -bn1 | grep "Cpu(s)"
%Cpu(s): 93.3 us,  5.7 sy,  0.0 ni,  1.0 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
yansendao at CompilerTest-aarch64-6:[jdk]> rm -rf tmp ; time jtreg -v1 -nr -w tmp test/hotspot/jtreg/gc/shenandoah/TestAllocObjectArrays.java#aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocObjectArrays.java#iu-aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocIntArrays.java#aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocIntArrays.java#iu-aggressive
Directory "tmp" not found: creating
Passed: gc/shenandoah/TestAllocIntArrays.java#aggressive
Passed: gc/shenandoah/TestAllocIntArrays.java#iu-aggressive
Passed: gc/shenandoah/TestAllocObjectArrays.java#aggressive
Passed: gc/shenandoah/TestAllocObjectArrays.java#iu-aggressive
Test results: passed: 4
Results written to /home/yansendao/git/jdk/tmp

real    1m49.423s
user    1m22.652s
sys     0m9.789s
yansendao at CompilerTest-aarch64-6:[jdk]> top -bn1 | grep "Cpu(s)"
%Cpu(s):  0.0 us,  0.2 sy,  0.0 ni, 99.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
yansendao at CompilerTest-aarch64-6:[jdk]> rm -rf tmp ; time jtreg -v1 -nr -w tmp test/hotspot/jtreg/gc/shenandoah/TestAllocObjectArrays.java#aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocObjectArrays.java#iu-aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocIntArrays.java#aggressive test/hotspot/jtreg/gc/shenandoah/TestAllocIntArrays.java#iu-aggressive
Directory "tmp" not found: creating
FAILED: gc/shenandoah/TestAllocIntArrays.java#aggressive
FAILED: gc/shenandoah/TestAllocIntArrays.java#iu-aggressive
FAILED: gc/shenandoah/TestAllocObjectArrays.java#aggressive
FAILED: gc/shenandoah/TestAllocObjectArrays.java#iu-aggressive
Test results: failed: 4
Results written to /home/yansendao/git/jdk/tmp
Error: Some tests failed or other problems occurred.

real    0m24.962s
user    3m31.204s
sys     0m8.073s


So, it seems that, if the cpu work quickly, there testcases failed; if the cpu work slowly, there testcases passed.

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

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