cc: Prevent unit tests from using Now() as the impl frame time.

cc/test/fake_layer_tree_host_impl.cc

Index: cc/test/fake_layer_tree_host_impl.cc
diff --git a/cc/test/fake_layer_tree_host_impl.cc b/cc/test/fake_layer_tree_host_impl.cc
index 7361794e7b1aa707018c8fe3a0f6214f5863ada6..84f75e0016a60efa06fb2da30bcc4658137b0c37 100644
--- a/cc/test/fake_layer_tree_host_impl.cc
+++ b/cc/test/fake_layer_tree_host_impl.cc
@@ -19,6 +19,10 @@ FakeLayerTreeHostImpl::FakeLayerTreeHostImpl(Proxy* proxy,
   // Explicitly clear all debug settings.
   SetDebugState(LayerTreeDebugState());
   SetViewportSize(gfx::Size(100, 100));
+
+  // Avoid using Now() as the frame time in unit tests.

[enne (OOO), 2014/08/06 23:49:38]

Random thought: is this something we could/should presubmit ban, in another
test?

[danakj, 2014/08/07 03:36:11]

Well. Its not the tests doing Now() explicitly. Its that they didn't set a
current frame time ticks. And LTHI uses Now(). Its horrible and we should make
LTHI stop using Now() really. Not sure how to guard this for other tests tho :/

+  base::TimeTicks time_ticks = base::TimeTicks::FromInternalValue(1);
+  SetCurrentFrameTimeTicks(time_ticks);
 }
 
 FakeLayerTreeHostImpl::FakeLayerTreeHostImpl(const LayerTreeSettings& settings,
@@ -32,6 +36,10 @@ FakeLayerTreeHostImpl::FakeLayerTreeHostImpl(const LayerTreeSettings& settings,
                         0) {
   // Explicitly clear all debug settings.
   SetDebugState(LayerTreeDebugState());
+
+  // Avoid using Now() as the frame time in unit tests.
+  base::TimeTicks time_ticks = base::TimeTicks::FromInternalValue(1);
+  SetCurrentFrameTimeTicks(time_ticks);
 }
 
 FakeLayerTreeHostImpl::~FakeLayerTreeHostImpl() {}