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

Damon Fenacci dfenacci at openjdk.org
Tue Sep 16 16:29:59 UTC 2025


## 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+

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

Commit messages:
 - JDK-8367278: reduce loop to 50 cycles
 - JDK-8367278: Test compiler/startup/StartupOutput.java timed out after completion on Windows

Changes: https://git.openjdk.org/jdk/pull/27254/files
  Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=27254&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8367278
  Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
  Patch: https://git.openjdk.org/jdk/pull/27254.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/27254/head:pull/27254

PR: https://git.openjdk.org/jdk/pull/27254


More information about the hotspot-compiler-dev mailing list