Avoid SYNC_CYCLE_CONTINUATION sync cycles

chrome/browser/sync/test/integration/migration_errors_test.cc

Index: chrome/browser/sync/test/integration/migration_errors_test.cc
diff --git a/chrome/browser/sync/test/integration/migration_errors_test.cc b/chrome/browser/sync/test/integration/migration_errors_test.cc
index d605e80cc1dc87fa0cbd394fa2fa87529054838d..97e76b9e4adcc7b11b357b864d1e6d591fbe45f4 100644
--- a/chrome/browser/sync/test/integration/migration_errors_test.cc
+++ b/chrome/browser/sync/test/integration/migration_errors_test.cc
@@ -171,7 +171,16 @@ class MigrationTest : public SyncTest {
     }
 
     // Phase 3: Wait for all clients to catch up.
-    ASSERT_TRUE(AwaitQuiescence());
+    //
+    // AwaitQuiescence() will not succeed when notifications are disabled.  We
+    // can safely avoid calling it because we know that, in the single client
+    // case, there is no one else to wait for.
+    //
+    // TODO(rlarocque, 97780): Remove the if condition when the test harness
+    // supports calling AwaitQuiescence() when notifications are disabled.
+    if (!do_test_without_notifications) {
+      AwaitQuiescence();
+    }
 
     // Re-enable notifications if we disabled it.
     if (do_test_without_notifications) {