[Reland] Per WebViewScheduler virtual time

third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp

Index: third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp
diff --git a/third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp b/third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp
index 6dc019faf1f46d191d072bd906a786711cf86051..2bc37726e720d139a213d247557c9d8a9d04c09d 100644
--- a/third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp
+++ b/third_party/WebKit/Source/platform/testing/UnitTestHelpers.cpp
@@ -54,6 +54,12 @@ void runPendingTasks()
     enterRunLoop();
 }
 
+void runTasksForPeriodInMilliseconds(double runTimeMilliseconds)
+{
+    Platform::current()->currentThread()->taskRunner()->postDelayedTask(BLINK_FROM_HERE, new QuitTask, runTimeMilliseconds);

[esprehn, 2016/02/23 10:30:11]

This is scary, what keeps this from being flaky?

[alex clarke (OOO till 29th), 2016/02/23 17:16:57]

Turns out we don't actually need this for
VirtualTimeTest.DOMTimersFireInExpectedOrder.

The other test which used this api (the non-virtual time case) isn't strictly
needed since there's a lot of test coverage elsewhere, so I've dropped it along
with runTasksForPeriodInMilliseconds.

+    enterRunLoop();
+}
+
 String blinkRootDir()
 {
     base::FilePath path;