Looks fine.
On 06/12/2017 05:20, Muneer Kolarkunnu wrote:
Hi Sergey,
I updated the webrev to incorporate your comment.
New webrev: http://cr.openjdk.java.net/~akolarkunnu/8191803/webrev/webrev.01/
I kept jtreg timeout as 4 minute by considering all other operations of the
test case.
Regards,
Hi Sergey,
I updated the webrev to incorporate your comment.
New webrev: http://cr.openjdk.java.net/~akolarkunnu/8191803/webrev/webrev.01/
I kept jtreg timeout as 4 minute by considering all other operations of the
test case.
Regards,
Muneer
-Original Message-
From: Sergey Bylokhov
> On Dec 4, 2017, at 10:54 AM, Phil Race wrote:
>
> 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.
I
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
Hello.
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
Hi,
Please review the fix for JDK-8191803.
Bug: https://bugs.openjdk.java.net/browse/JDK-8191803
Webrev: http://cr.openjdk.java.net/~akolarkunnu/8191803/webrev/webrev.00/
Issue: In usual ways itself, it is taking 30-40 seconds to complete the
progress bar. So in slow machines it may