Mark Art053-wait-some test as flaky
The test is failing often by exceeding the threshold of 500 ms on our
buildbots. Lastly it failed because it took 502 ms.
Change-Id: I8ea2be6a4a1a3a931855197258fe97b3971ffff9
diff --git a/src/test/java/com/android/tools/r8/R8RunArtTestsTest.java b/src/test/java/com/android/tools/r8/R8RunArtTestsTest.java
index afba9d9..11dc790 100644
--- a/src/test/java/com/android/tools/r8/R8RunArtTestsTest.java
+++ b/src/test/java/com/android/tools/r8/R8RunArtTestsTest.java
@@ -197,6 +197,9 @@
// printWeakReference on lines Main.java:78-79. An expected flaky
// result contains: "but was:<wimp: [null]".
.put("036-finalizer", TestCondition.any())
+ // The test waits for a maximum of 500 ms which is unreliable when running on buildbots:
+ // Elapsed time was too long: elapsed=552 max=550
+ .put("053-wait-some", TestCondition.any())
// Failed on buildbot with: terminate called after throwing an instance
// of '__gnu_cxx::recursive_init_error'
.put("096-array-copy-concurrent-gc",
