<Swing Dev>  RFR JDK-8191803 : [TEST_BUG] : sanity/client/SwingSet/src/ProgressBarDemoTest.java failed with "Wait "greater then 1349" state to be reached
philip.race at oracle.com
Mon Dec 4 18:54:47 UTC 2017
From memory, I think Sergey is right that the jtreg default time out is
2 minutes (120 seconds).
As to changing that to 3 minutes .. that is something that needs to be
decided at a jtreg ownership level.
A little off topic, but I've sometimes pondered if jtreg ought to have
an option to avoid running lengthy tests,
when time is of the essence. e.g., any test that specifies a timeout
greater than the default.
But if only a few percent of tests do that it probably does not make
enough difference to matter.
On 12/04/2017 10:29 AM, Sergey Bylokhov wrote:
> On 03/12/2017 22:54, Muneer Kolarkunnu wrote:
>> Issue: In usual ways itself, it is taking 30-40 seconds to complete
>> the progress bar. So in slow machines it may take more time. Default
>> timeout is 1 minute. Also in the screen shots, it is visible that
>> demo is not blocked anywhere, it is still continuing, but failed due
>> to timeout.
> As far as I know that jtreg by default has 2 minute timeout, should it
> also be changed to 3 minutes?
More information about the swing-dev