On Wed, 22 Apr 2026 08:14:12 GMT, Per Minborg <[email protected]> wrote:
>> test/jdk/java/lang/LazyConstant/LazyConstantSafePublicationTest.java line
>> 154:
>>
>>> 152: try {
>>> 153: for (Thread t:threads) {
>>> 154: long deadline = System.nanoTime() +
>>> TimeUnit.MINUTES.toNanos(4);
>>
>> Maybe we can use the API jdk.test.lib.Utils.adjustTimeout to multiply the
>> jtreg timeout factor.
>
> This test has its own "give up" logic. I believe the standard timeout is 480s
> (8 minutes).
I think you misundertood what I mean.
4 Noaos maybe enough for release build, but maybe not enough for fastdebug
build. When the tested jdk is fastdebug build, we increase the jtreg timeout
factor(jtreg -timeoutFactor:4/8 etc..) generally. So it will be useful to read
the timeout factor and multiply it.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/30832#discussion_r3122664241
