RFR: 8367278: Test compiler/startup/StartupOutput.java timed out after completion on Windows [v2]

[Christian Hagedorn]

On Wed, 17 Sep 2025 14:17:13 GMT, Damon Fenacci <dfenacci at openjdk.org> wrote:

>> ## Problem
>> After [JDK-8260555](https://bugs.openjdk.org/browse/JDK-8260555) changed the default TIMEOUT_FACTOR from 4 to 1, the test compiler/startup/StartupOutput.java can occasionally slightly exceed the 2-minute timeout on Windows.
>> 
>> ## Change
>> Rather than increasing the timeout, this change reduces the number of VM runs with randomly generated near-minimum code cache sizes from 200 to 50. This should still provide sufficient coverage while keeping execution well within the timeout.
>> 
>> ## Testing:
>> Tiers 1-3+
>
> Damon Fenacci 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 'master' into JDK-8367278
>  - JDK-8367278: reduce loop to 50 cycles
>  - JDK-8367278: Test compiler/startup/StartupOutput.java timed out after completion on Windows

That looks reasonable to me, thanks for fixing it!

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

Marked as reviewed by chagedorn (Reviewer).

PR Review: https://git.openjdk.org/jdk/pull/27254#pullrequestreview-3234935299