On Thu, 11 Aug 2022 20:02:06 GMT, Daniel D. Daugherty <dcu...@openjdk.org>
wrote:
> A trivial fix so that Continuation/Fuzz.java honors the timeoutFactor JTREG
> setting
> when waiting for a compilation to finish.
>
> This fix is being tested in my jdk-20+10 stress testing run.
>
> The usual Mach5 timeoutFactor is 4.0 with slower configurations using a
> timeoutFactor
> of 10.0. In my stress testing, I use release-bits: 4.0, fastdebug-bits: 6.0
> and slowdebug-bits: 12.0.
@lmesnik, @DamonFool and @AlanBateman - Thanks for the reviews.
test/jdk/jdk/internal/vm/Continuation/Fuzz.java line 82:
> 80:
> 81: static float timeoutFactor =
> Float.parseFloat(System.getProperty("test.timeout.factor", "1.0"));
> 82: static final int COMPILATION_TIMEOUT = (int)(1_000 * timeoutFactor);
> // ms
I was really hoping that `1_000 * timeoutFactor` would do the trick,
but stress run-#1 on my macosx-aarch64 machine had a couple of
sub-test timeouts at 12 seconds (1_000 * 12.0). My timeoutFactor
for slowdebug is 12.0. My linux-x64 machine passed stress run-#1
without any failures.
I've switched the value from 1_000 back to 5_000 for the next two
stress runs on both machines.
-------------
PR: https://git.openjdk.org/jdk/pull/9844
