On Thu, 11 Sep 2025 09:34:59 GMT, Raffaello Giulietti <[email protected]> 
wrote:

>> test/jdk/java/math/BigInteger/BigIntegerTest.java line 32:
>> 
>>> 30:  * @library /test/lib
>>> 31:  * @build jdk.test.lib.RandomFactory
>>> 32:  * @run main/timeout=480 BigIntegerTest
>> 
>> Should the timeoutFactor change have adjusted this from 400 to 1600?
>
> There were two `@run` lines, one without a timeout (which is now removed), 
> and a later one with a timeout of 400.
> IIUC, this means that the test was executed 2 times, one with a default 
> timeout, and another with the explicit timeout of 400.
> 
> The JBS issue shows a timeout after 120 seconds, so I guess this was due to 
> the first `@run` line without an explicit timeout.

Yes - the observed timeout was 120s - so it must have been the first `@run`.  
That first `@run` was added by 
[JDK-8078672](https://bugs.openjdk.org/browse/JDK-8078672) - I'm not sure why - 
that might have been a left over from debugging...

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

PR Review Comment: https://git.openjdk.org/jdk/pull/27211#discussion_r2340093654

Reply via email to