8022206: Intermittent test failures in java/lang/ProcessBuilder/Basic.java

Martin Buchholz martinrb at google.com
Tue Nov 19 20:14:45 UTC 2013

In jsr166 tests we have mostly switched to 10 second timeouts to mean
But in ProcessBuilder tests we are starting up new java processes with
their well-known startup problems, so using a much larger value of
"forever" seems reasonable.  I vote for 1 minute.  You can write

waitFor(1, TimeUnit.MINUTES);

On Tue, Nov 19, 2013 at 7:05 AM, Alan Bateman <Alan.Bateman at oracle.com>wrote:

> On 19/11/2013 14:28, Rob McKenna wrote:
>> Hi folks,
>> Looking for a quick review for a test failure we're encountering.
>> Seemingly no bar is too high for our test infrastructure. Hopefully this
>> will put this particular failure to rest.
>> http://cr.openjdk.java.net/~robm/8022206/webrev.01/
>> https://bugs.openjdk.java.net/browse/JDK-8022206
> It's hard to believe that the 10s is exceeded but the change is harmless
> (and hence okay).
> -Alan

More information about the core-libs-dev mailing list