Passing time factor to tests run under jtreg

Alan Bateman Alan.Bateman at
Thu Nov 17 23:16:51 UTC 2011

On 17/11/2011 20:28, Gary Adams wrote:
> :
> In general it seems that tests that declare a timeout less than 120
> seconds are indicating that an early termination for the test  is 
> acceptable.
> Tests declaring a longer than 120 second timeout recognize that 
> additional
> processing time may be required.
I can't think of any need for tests to specify a timeout less then the 
default. When fixing a deadlock or some such bug then you will typically 
run the test with a JDK build that doesn't have the fix and a JDK build 
with the fix. When testing with the former then it's nice to have the 
test timeout quickly which is why some tests do have a short timeout. 
But since the bugs are long fixed then these tests should not hang or 
deadlock and so the default timeout should be fine. Clearly 
slower/stress tests that have the potential to excess the default 
timeout need to override the default timeout.

In any case, for 300Mhz then I would definitely run with 
-timeoutFactor:2 or greater. A useful file to look at is 
JTreport/text/timeStats.txt as it shows the distribution of the test 
execution times.


More information about the core-libs-dev mailing list