Closed Bug 1428803 Opened 7 years ago Closed 7 years ago

Intermittent dom/animation/test/mozilla/test_restyles.html | Animations running on the main-thread which were in scrolled out elements should update restyling soon after the element moved in view by scrolling - got +0, expected 5

Categories

(Core :: DOM: Animation, defect, P5)

Product:
Core
Component:
DOM: Animation
Type:
defect

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure)

Filed by: archaeopteryx [at] coole-files.de https://treeherder.mozilla.org/logviewer.html#?job_id=154656790&repo=autoland https://queue.taskcluster.net/v1/task/L8OCmVUMRTCFhs3rfkK1XA/runs/0/artifacts/public/logs/live_backing.log [task 2018-01-08T01:54:06.144Z] 01:54:06 INFO - 141 INFO TEST-PASS | dom/animation/test/mozilla/test_restyles.html | Animations running on the main-thread for elements which are scrolled out should never cause restyles [task 2018-01-08T01:54:06.144Z] 01:54:06 INFO - Buffered messages finished [task 2018-01-08T01:54:06.145Z] 01:54:06 INFO - 142 INFO TEST-UNEXPECTED-FAIL | dom/animation/test/mozilla/test_restyles.html | Animations running on the main-thread which were in scrolled out elements should update restyling soon after the element moved in view by scrolling - got +0, expected 5 [task 2018-01-08T01:54:06.145Z] 01:54:06 INFO - SimpleTest.is@SimpleTest/SimpleTest.js:312:5 [task 2018-01-08T01:54:06.145Z] 01:54:06 INFO - restyling_main_thread_animations_in_scrolled_out_element@dom/animation/test/mozilla/file_restyles.html:518:5
I suspected this started from https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=92ff8af42f6fd6db6e7255b287031d6ec298e031 but it's not. 　This failure happened on the previous commit https://treeherder.mozilla.org/#/jobs?repo=autoland&tochange=92ff8af42f6fd6db6e7255b287031d6ec298e031&fromchange=ef89f9d60f81063ac58fdcae049792d6e59a3233&selectedJob=154837709 . That's said, the revision 92ff8af42f6fd6db6e7255b287031d6ec298e031 made the failure more frequent? CCing kats.
It didn't look like you had enough retriggers to conclude anything meaningful about frequency so I did a bunch more retriggers. Some of the retriggers died due to the infra problems we've been having today, but even so, I don't think my patches significantly affected the frequency of this. Note that there was an instance of the failure on d6993ed46421 as well which was a few pushes earlier than mine. https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=Android%204.3%20API16%2B%20debug%20Mochitests%20executed%20by%20TaskCluster%20test-android-4.3-arm7-api-16%2Fdebug-mochitest-2%20tc-M(2)&tochange=92ff8af42f6fd6db6e7255b287031d6ec298e031&fromchange=ef89f9d60f81063ac58fdcae049792d6e59a3233&group_state=expanded
Also just based on the nature of the test and my patches I don't think it's likely that my patches would have affected this test. There *was* a regression from my patches which I addressed in bug 1428765 (on autoland now) so if you still feel my patches might have affected this test we can do retriggers around that bug to see if it reduced the frequency.
Thank you kats for retriggering and the info! In any cases, I have to investigate why the test cases fails on Android.
Flags: needinfo?(hikezoe)
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(hikezoe)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.