Fix failing (flaky) LayerTreeHostTestLCDNotification test.

cc/scheduler/scheduler.h

Index: cc/scheduler/scheduler.h
diff --git a/cc/scheduler/scheduler.h b/cc/scheduler/scheduler.h
index afb9e9d0e8e54ec6f689d13ee2c0333b9deeef9c..f6dd2bcf4ec36063c21d5fa380864d51db59eef8 100644
--- a/cc/scheduler/scheduler.h
+++ b/cc/scheduler/scheduler.h
@@ -98,6 +98,13 @@ class CC_EXPORT Scheduler {
   void DidLoseOutputSurface();
   void DidCreateAndInitializeOutputSurface();
 
+  // Tests do not want to shut down until all possible BeginMainFrames have
+  // occured to prevent flakiness.
+  bool MainFrameForTestingWillHappen() const {

[enne (OOO), 2014/08/11 19:50:12]

bikeshed: Will => Could?

[danakj, 2014/08/11 20:01:06]

I had that at first, but it definitely will come, just maybe not right *now*,
cuz needs_commit_ is true so it'll come next vsync or something. So.. idk, I
slightly prefer Will over Could for this.

[enne (OOO), 2014/08/11 20:05:02]

Ok, sure.  :)

+    return state_machine_.CommitPending() ||
+           state_machine_.CouldSendBeginMainFrame();
+  }
+
   bool CommitPending() const { return state_machine_.CommitPending(); }
   bool RedrawPending() const { return state_machine_.RedrawPending(); }
   bool ManageTilesPending() const {