RFR: 8366692: Several gc/shenandoah tests timed out

[SendaoYan]

On Tue, 2 Sep 2025 18:21:14 GMT, William Kemper <wkemper at openjdk.org> wrote:

>> Hi all,
>> 
>> After JDK-8260555 set the default jtreg timeout factor to 1, then several gc/shenandoah tests run timed out with jtreg options -timeoutFactor:1. So I think it's necessary to increase the timeout value set in tests to make test run normally.
>> 
>> The actual run time consumed on my linux-x64 machine with  224 CPU core threads shows in [JDK-8366692](https://bugs.openjdk.org/browse/JDK-8366692).
>> 
>> Accodring the time statistics, the test test/hotspot/jtreg/gc/shenandoah/TestSieveObjects.java only change the second `@run` at the `@test id=generational` and `@test id=aggressive`, other tests do not need to change. And all the `@run` in test test/hotspot/jtreg/gc/shenandoah/jni/TestJNIGlobalRefs.java changed from 120(default value) to 240.
>> 
>> Change has been verified locally on linux-x64, test-fix only, no risk.
>
> Seems there is some unrelated build breakage. Can we merge from `master` again before integrating?

Thanks for the reviews @earthling-amzn @shipilev

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

PR Comment: https://git.openjdk.org/jdk/pull/27052#issuecomment-3251359877