cc: Heuristic for Renderer latency recovery

cc/test/begin_frame_args_test.cc

Index: cc/test/begin_frame_args_test.cc
diff --git a/cc/test/begin_frame_args_test.cc b/cc/test/begin_frame_args_test.cc
index 7b2974867469d3803d029dedc483dff233290edb..fc7e78f3444b35764edc5c9b83def83111982e65 100644
--- a/cc/test/begin_frame_args_test.cc
+++ b/cc/test/begin_frame_args_test.cc
@@ -20,7 +20,8 @@ BeginFrameArgs CreateBeginFrameArgsForTesting(
     base::TimeTicks frame_time) {
   return BeginFrameArgs::Create(
       location, frame_time,
-      frame_time + (BeginFrameArgs::DefaultInterval() / 2),
+      frame_time + BeginFrameArgs::DefaultInterval() -
+          BeginFrameArgs::DefaultEstimatedParentDrawTime(),

[brianderson, 2015/05/08 16:52:50]

I changed this because the non-zero threshold in
Scheduler::CanDrawBeforeDeadline made it difficult for my unittests to make
CanDrawBeforeDeadline true if the deadline was half way through the frame.

I could have made it work in the tests with really small duration estimates, but
decided to change this instead since it better reflects the BeginFrames we'd get
in production with hard coded deadlines.

       BeginFrameArgs::DefaultInterval(), BeginFrameArgs::NORMAL);
 }