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

[SendaoYan]

On Tue, 25 Jun 2024 19:36:38 GMT, Y. Srinivas Ramakrishna <ysr at openjdk.org> wrote:

> > Can they remain enabled until JDK-8332031 is fixed? Is there a clear need to problem-list them now?
> 
> For example, could you run on your machine/failure scenarios with a large timeout, a larger ShenandoahNoProgressThreshold and/or a smaller ShenandoahCriticalFreeThreshold ?
> 
> cc @kdnilsen who's looking at GC progress related OOM throwing separately for his thinking.
> 
> If we believe problem-listing them provides some immediate value to us, I am happy to sponsor, but that was not clear to me from preceding discussion.

Thanks for the advice. Run with larger timeout can avoid the OOM failure. A larger ShenandoahNoProgressThreshold and/or a smaller ShenandoahCriticalFreeThreshold can avoid the OOM failure.

These two testcase has more than `#aggressive`, `#iu-aggressive` test tags, also has `#passive`, `#adaptive` etc. test tags, problemlist the failure scenarios will make the CI less noisy and catch new failure more efficiency.

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

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