On Wed, 25 Aug 2021 15:56:39 GMT, Igor Ignatyev <iignat...@openjdk.org> wrote:
> so instead of using the hardcode limit, I'd prefer to adjust the > multiplication, `0.25` will give you the same 60s w/ current default timeout > factor. Oh, okay, good point. I changed multiplier from `0.9` to `0.2`. That works out to ~75 seconds per actual test, and 90 seconds for entire run: ----------messages:(5/416)---------- command: main -XX:ReservedCodeCacheSize=128m LFSingleThreadCachingTest reason: User specified action: run main/othervm -XX:ReservedCodeCacheSize=128m LFSingleThreadCachingTest Mode: othervm [/othervm specified] Additional options from @modules: --add-modules java.base,java.management --add-opens java.base/java.lang.ref=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED elapsed time (seconds): 76.789 ... real 1m38.629s user 2m55.333s sys 0m5.318s ------------- PR: https://git.openjdk.java.net/jdk/pull/5214
