Closed Bug 1413370 Opened 2 years ago Closed Last year
_restyles .html | Transform animation running on the element which is scrolled out should be unthrottled after around 200ms have elapsed . now: 21960 .83704899999 start time: 21741 .96209899999 - got +0, expected 1
59 bytes, text/x-review-board-request
From a failure log; https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=142279477&lineNumber=2080 now: 8691.369961 start time: 8365.742072 - got +0, expected 1 This means that the last CanThrottle() was called within 200ms but the next requestAnimationFrame and a Promise took over 100ms? I am wondering bug 1193394 fixes this skew? I hope it does.
41 Total failures in the last week. Occurrences per platform: - 36 android-4-3-armv7-api16 - 5 android-api-16-gradle Occurrences per build type: - 30 debug - 11 opt Here is a recent log: https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=147291318&lineNumber=1861 and a relevant snippet from it: [task 2017-11-24T01:24:33.117Z] 01:24:33 INFO - 130 INFO SpawnTask.js | Entering test restyling_transform_animations_in_scrolled_out_element 1859 [task 2017-11-24T01:24:33.118Z] 01:24:33 INFO - 131 INFO TEST-PASS | dom/animation/test/mozilla/test_restyles.html | The transform animation is not running on the compositor 1860 [task 2017-11-24T01:24:33.119Z] 01:24:33 INFO - Buffered messages finished 1861 [task 2017-11-24T01:24:33.119Z] 01:24:33 INFO - 132 INFO TEST-UNEXPECTED-FAIL | dom/animation/test/mozilla/test_restyles.html | Transform animation running on the element which is scrolled out should be unthrottled after around 200ms have elapsed. now: 19617.769936999997 start time: 19417.448469 - got +0, expected 1 1862 [task 2017-11-24T01:24:33.119Z] 01:24:33 INFO - SimpleTest.is@SimpleTest/SimpleTest.js:312:5 1863 [task 2017-11-24T01:24:33.120Z] 01:24:33 INFO - restyling_transform_animations_in_scrolled_out_element@dom/animation/test/mozilla/file_restyles.html:337:7 1864 [task 2017-11-24T01:24:33.121Z] 01:24:33 INFO - 133 INFO SpawnTask.js | Leaving test restyling_transform_animations_in_scrolled_out_element
Whiteboard: [stockwell needswork]
This is the test added in bug 1190721. If we can't look into this soon, we should just disable this test on Android.
I am hoping this intermittent is fixed by bug 1413817, but unfortunately it will not be fixed soonish. I am going to disable the test case on Android. One thing I am really curios is that the failure is getting more frequent recently, why?
Boris, would you mind reviewing this since Brian is PTO today.
Comment on attachment 8931975 [details] Bug 1413370 - Drop isAndroid variable in file_restyles.html. https://reviewboard.mozilla.org/r/203026/#review208342 Seems Bug 1413817 will fix this. :)
Attachment #8931975 - Flags: review?(boris.chiou) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/f195d80f0bde Skip the test case that checks transform animation on scrolled-out element is unthrottled periodically on Android. r=boris
Whiteboard: [stockwell needswork] → [stockwell disabled]
This failure should no longer happen. And I forgot to drop isAndroid variable in file_restyles.html in bhttps://reviewboard.mozilla.org/r/247764/diff/#index_header . I will use this bug for dropping the variable.
Assignee: nobody → hikezoe
Status: NEW → ASSIGNED
Comment on attachment 8931975 [details] Bug 1413370 - Drop isAndroid variable in file_restyles.html. https://reviewboard.mozilla.org/r/203026/#review254236
Attachment #8931975 - Flags: review?(bbirtles) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/3fcae880dff8 Drop isAndroid variable in file_restyles.html. r=birtles,boris
Status: ASSIGNED → RESOLVED
Closed: Last year
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.