Don't call Timer::Stop() off-sequence in SyncBrowserThreadModelWorkerTest

components/sync/engine/browser_thread_model_worker_unittest.cc

Index: components/sync/engine/browser_thread_model_worker_unittest.cc
diff --git a/components/sync/engine/browser_thread_model_worker_unittest.cc b/components/sync/engine/browser_thread_model_worker_unittest.cc
index 4e3c01fa38a03bceaefd4034246d89d943f6eeb8..f05d2b8795c640082608ea29036cf96cdef0a58d 100644
--- a/components/sync/engine/browser_thread_model_worker_unittest.cc
+++ b/components/sync/engine/browser_thread_model_worker_unittest.cc
@@ -50,7 +50,6 @@ class SyncBrowserThreadModelWorkerTest : public testing::Test {
   // This is the work that will be scheduled to be done on the DB thread.
   SyncerError DoWork() {
     EXPECT_TRUE(db_thread_.task_runner()->BelongsToCurrentThread());
-    timer_.Stop();  // Stop the failure timer so the test succeeds.

[stanisc, 2017/01/25 00:55:16]

Would it make sense to remove timer_ completely and just rely on test timeout?

[gab, 2017/01/25 14:51:47]

Yes it does but since there are many erroneous cases around I was hoping to just
do the minimal change to get things correct and have owners improve further on
their own timeline should they care

     main_message_loop_.task_runner()->PostTask(
         FROM_HERE, base::MessageLoop::QuitWhenIdleClosure());
     did_do_work_ = true;