Code Review - 6736316 TEST_BUG: Timeout value in java/util/concurrent/locks/Lock/ is insufficient

Gary Adams gary.adams at
Mon Nov 21 19:26:27 UTC 2011

  The original complaint about the flakey mutex regression test is
that it was failing on slower machines. The delay at the end of
the processing is unnecessarily restrictive. Since the test harness
will terminate after 120 seconds if the test hangs, the test does
not have to terminate more quickly.

Here's a propose compromise that allows the service up to 120 seconds
to terminate and allows an early exit if the service completes sooner.
Alternatively, we could just increase the timeout to the full 120 seconds
which will also exit sooner if the service completes earlier.

More information about the core-libs-dev mailing list