On 7/9/2014 2:32 AM, Daniel Fuchs wrote:
On 7/9/14 5:46 AM, Mandy Chung wrote:
Do you know if the test was run with -timeoutFactor? Or does it use
the default timeout? Are you able to run the test with the same
configuration (on same test machine) to see how long it takes?
...
What I can
On 7/9/14 5:46 AM, Mandy Chung wrote:
On 7/8/2014 5:58 AM, Daniel Fuchs wrote:
Hi,
Please find below a fix for
8048913: java/util/logging/LoggingDeadlock2.java times out
http://cr.openjdk.java.net/~dfuchs/webrev_8048913/webrev.00/
My suggestion is thus simply to remove the /timeout=1
On 8/07/2014 10:58 PM, Daniel Fuchs wrote:
Hi,
Please find below a fix for
8048913: java/util/logging/LoggingDeadlock2.java times out
http://cr.openjdk.java.net/~dfuchs/webrev_8048913/webrev.00/
jdk/test/java/util/logging/LoggingDeadlock2.java has been seen failing
in timeout in some of our
On 7/8/2014 5:58 AM, Daniel Fuchs wrote:
Hi,
Please find below a fix for
8048913: java/util/logging/LoggingDeadlock2.java times out
http://cr.openjdk.java.net/~dfuchs/webrev_8048913/webrev.00/
My suggestion is thus simply to remove the /timeout=15 from the
@run command line, relying o
Hi,
Please find below a fix for
8048913: java/util/logging/LoggingDeadlock2.java times out
http://cr.openjdk.java.net/~dfuchs/webrev_8048913/webrev.00/
jdk/test/java/util/logging/LoggingDeadlock2.java has been seen failing
in timeout in some of our internal nightly builds.
java/util/logging/
