Increase the wait time for assertDurationIsInRange(0)
Addressing flakiness in test_parkFor_3 / test_parkUntil_3.
The wait time permitted was Math.max(expectedMillis * 10, 30)
where expectedMillis = 0. That meant that the test code had
just 30ms between calling Thread.start() and the Parker code being
executed reaching the notifyAll().
Other tests use an expectedMillis of 500 and 300, giving
more time for the Thread to start and complete their wait().
e.g. 4500ms and 2700ms above the expected park time,
respectively.
Bug: 29177727
(cherry picked from commit fe71cd583ca8f5709b25190acc48b28180e192b7)
Change-Id: I82bbd8a6d252ee89a147b671799e4a64e2f7feac
diff --git a/harmony-tests/src/test/java/org/apache/harmony/tests/org/apache/harmony/kernel/dalvik/ThreadsTest.java b/harmony-tests/src/test/java/org/apache/harmony/tests/org/apache/harmony/kernel/dalvik/ThreadsTest.java
index 3ee50fe..37c6086 100644
--- a/harmony-tests/src/test/java/org/apache/harmony/tests/org/apache/harmony/kernel/dalvik/ThreadsTest.java
+++ b/harmony-tests/src/test/java/org/apache/harmony/tests/org/apache/harmony/kernel/dalvik/ThreadsTest.java
@@ -237,7 +237,7 @@
long minimum = (long) ((double) expectedMillis * 0.80);
long maximum =
Math.max((long) ((double) expectedMillis * 1.20), 10);
- long waitMillis = Math.max(expectedMillis * 10, 30);
+ long waitMillis = Math.max(expectedMillis * 10, 1000);
long duration = getDurationMillis(waitMillis);
if (duration < minimum) {
