RFR: 8367278: Test compiler/startup/StartupOutput.java timed out after completion on Windows
Damon Fenacci
dfenacci at openjdk.org
Thu Sep 18 06:27:45 UTC 2025
On Wed, 17 Sep 2025 13:10:33 GMT, SendaoYan <syan 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+
>
> GHA shows GetStackTraceALotWhenPinned.java timed out on macos. The failure has been fixed by [JDK-8366893](https://bugs.openjdk.org/browse/JDK-8366893). I think you can merge the master first.
Thanks for your reviews @sendaoYan @chhagedorn.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/27254#issuecomment-3305596171
More information about the hotspot-compiler-dev
mailing list