RFR: 8366692: Several gc/shenandoah tests timed out [v2]

[SendaoYan]

On Wed, 3 Sep 2025 02:00:24 GMT, SendaoYan <syan 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.
>
> SendaoYan has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains three additional commits since the last revision:
> 
>  - Merge branch 'openjdk:master' into jbs8366692
>  - add timeout value for @aggressive
>  - 8366692: Several gc/shenandoah tests timed out

Sorry, I missed the another timed out test gc/shenandoah/TestAllocObjects.java#aggressive.

The time statistics show that the first two '@run' consume time about 145.316 and 260.58. So I think we should change the timed out value to 240 and 480.

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

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