Bug 1254840 - Use longer animation duration to avoid intermittent failures on slow platforms. r=dholbert

MozReview-Commit-ID: FXrO0yI7Irt

--HG--
extra : rebase_source : dc9a4b629d9cb34821e0ba2ae2108454a9781805

dom/animation/test/chrome/test_restyles.html

@@ -348,16 +348,19 @@ waitForAllPaints(function() {
 
   add_task_if_omta_enabled(function* change_duration_and_currenttime() {
     var div = addDiv(null);
-    var animation = div.animate({ opacity: [ 0, 1 ] }, 10000);
+    var animation = div.animate({ opacity: [ 0, 1 ] }, 100000); //100s
 
     yield animation.ready;
     ok(animation.isRunningOnCompositor);
 
-    animation.currentTime = 50000;
+    // Set currentTime to a time longer than duration.
+    animation.currentTime = 500000; // 500s
 
+    // Now the animation immediately get back from compositor.
     ok(!animation.isRunningOnCompositor);
 
-    animation.effect.timing.duration = 100000;
+    // Extend the duration.
+    animation.effect.timing.duration = 800000; // 800s
     var markers = yield observeStyling(5);
     is(markers.length, 1,
        'Animations running on the compositor should update style ' +