Adding tests that would reliably reproduce shifted search.

This would guaranteed to repro b/118441555 before it was fixed.

The test doesn't use the most powerful feature of race condition
reproducer, which is enumerating all possible event sequences.

Instead, it uses explicit repro sequences, which makes the test much
faster.

Bug: 120628042
Test: The added test
Change-Id: I89a7a9964f160a8a20ba3d9dda2f248237713014

1 files changed, 9 insertions, 0 deletions

diff --git a/tests/src/com/android/launcher3/util/RaceConditionReproducer.java b/tests/src/com/android/launcher3/util/RaceConditionReproducer.java
index c4350de0b..316e40d82 100644
--- a/tests/src/com/android/launcher3/util/RaceConditionReproducer.java
+++ b/tests/src/com/android/launcher3/util/RaceConditionReproducer.java
@@ -43,6 +43,11 @@ import java.util.concurrent.TimeUnit;
  * executing events in previously unseen order. It does it by postponing execution of threads that
  * would lead to an already seen sequence.
  *
+ * If an event A occurs before event B in the sequence, this is how execution order looks like:
+ * Events: ... A ... B ...
+ * Events and instructions, guaranteed order:
+ *   (instructions executed prior to A) A ... B (instructions executed after B)
+ *
  * Each iteration has 3 parts (phases).
  * Phase 1. Picking a previously seen event subsequence that we believe can have previously unseen
  * continuations. Reproducing this sequence by pausing threads that would lead to other sequences.
@@ -178,6 +183,10 @@ public class RaceConditionReproducer implements RaceConditionTracker.EventProces
         mReproString = reproString;
     }
 
+    public RaceConditionReproducer(String... reproSequence) {
+        this(String.join("|", reproSequence));
+    }
+
     public synchronized String getCurrentSequenceString() {
         return mCurrentSequence.toString();
     }