Closed Bug 1583969 Opened 6 months ago Closed 6 months ago

Intermittent /svg/animations/scripted/onhover-syncbases.html | Check if onhover events reset correctly when triggered multiple times - assert_equals: expected "rgb(255, 0, 0)" but got "rgb(0, 255, 0)"

Categories

(Core :: SVG, defect, P5)

defect

Tracking

()

RESOLVED FIXED
mozilla71
Tracking Status
firefox-esr60 --- unaffected
firefox-esr68 --- unaffected
firefox67 --- unaffected
firefox68 --- unaffected
firefox69 --- unaffected
firefox70 --- unaffected
firefox71 --- fixed

People

(Reporter: intermittent-bug-filer, Assigned: dholbert)

References

(Regression)

Details

(Keywords: intermittent-failure, regression)

Attachments

(1 file)

Filed by: apavel [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=268411107&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/R3FxDHmVTfiXqHkm-HVigg/runs/0/artifacts/public/logs/live_backing.log


[task 2019-09-25T18:28:26.226Z] 18:28:26 INFO - TEST-START | /svg/animations/scripted/onhover-syncbases.html
[task 2019-09-25T18:28:26.231Z] 18:28:26 INFO - Closing window 29
[task 2019-09-25T18:28:26.269Z] 18:28:26 INFO - PID 6932 | [Parent 9252, Gecko_IOThread] WARNING: pipe error: 109: file z:/task_1569425148/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
[task 2019-09-25T18:28:26.269Z] 18:28:26 INFO - PID 6932 | [Child 4980, Chrome_ChildThread] WARNING: pipe error: 109: file z:/task_1569425148/build/src/ipc/chromium/src/chrome/common/ipc_channel_win.cc, line 341
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO -
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - TEST-UNEXPECTED-FAIL | /svg/animations/scripted/onhover-syncbases.html | Check if onhover events reset correctly when triggered multiple times - assert_equals: expected "rgb(255, 0, 0)" but got "rgb(0, 255, 0)"
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - f@http://web-platform.test:8000/svg/animations/scripted/onhover-syncbases.html:24:18
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step_timeout/<@http://web-platform.test:8000/resources/testharness.js:1963:22
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1905:25
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step_func/<@http://web-platform.test:8000/resources/testharness.js:1929:35
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - setTimeout handlerTest.prototype.step_timeout@http://web-platform.test:8000/resources/testharness.js:1962:16
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - f/<@http://web-platform.test:8000/svg/animations/scripted/onhover-syncbases.html:36:11
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step_timeout/<@http://web-platform.test:8000/resources/testharness.js:1963:22
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1905:25
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step_func/<@http://web-platform.test:8000/resources/testharness.js:1929:35
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - setTimeout handler
Test.prototype.step_timeout@http://web-platform.test:8000/resources/testharness.js:1962:16
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - f@http://web-platform.test:8000/svg/animations/scripted/onhover-syncbases.html:32:7
[task 2019-09-25T18:28:26.522Z] 18:28:26 INFO - Test.prototype.step_timeout/<@http://web-platform.test:8000/resources/testharness.js:1963:22
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1905:25
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - Test.prototype.step_func/<@http://web-platform.test:8000/resources/testharness.js:1929:35
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - setTimeout handler*Test.prototype.step_timeout@http://web-platform.test:8000/resources/testharness.js:1962:16
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - @http://web-platform.test:8000/svg/animations/scripted/onhover-syncbases.html:39:5
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - Test.prototype.step@http://web-platform.test:8000/resources/testharness.js:1905:25
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - async_test@http://web-platform.test:8000/resources/testharness.js:576:22
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - @http://web-platform.test:8000/svg/animations/scripted/onhover-syncbases.html:19:11
[task 2019-09-25T18:28:26.523Z] 18:28:26 INFO - TEST-OK | /svg/animations/scripted/onhover-syncbases.html | took 295ms

FWIW, this test already has a complex constellation of known-failure annotations at
https://searchfox.org/mozilla-central/rev/f43ae7e1c43a4a940b658381157a6ea6c5a185c1/testing/web-platform/meta/svg/animations/scripted/onhover-syncbases.html.ini

In fact, it looks like we initially tried to disable this failing check entirely ("disabled: true" in that .ini file), but we had a typo in the log-matching-string ("triggred", which is misspelled in that .ini file -- it's missing the "e" after "gg"), so it probably doesn't ever take effect.

There's another less-generous set of annotations further down (which are active due to having the correctly-spelled log message), and that lower section has some known-failures annotated for WebRender configurations. But this particular failure in comment 0 was on a platform that did not have webrender, I think (at least, no "qr" in the jobname), which is why it was expected to pass.

We probably need to update the expectations, and perhaps remove the webrender check in the Windows annotation here.

Hi Daniel, is that something you are working on or who can I ni?

Flags: needinfo?(dholbert)
Regressed by: 1582450

For now, I think we need to just fix the failure annotation to reflect the reality of where this test fails.

I don't have cycles to investigate the test failure itself - as I recall, it was already failing when we imported it from upstream WPT. I can take a lok at fixing the annotations sometime early this week, though.

(In reply to Daniel Holbert [:dholbert] from comment #3)

For now, I think we need to just fix the failure annotation to reflect the reality of where this test fails.

I don't have cycles to investigate the test failure itself - as I recall, it was already failing when we imported it from upstream WPT. I can take a lok at fixing the annotations sometime early this week, though.

Sounds good, thank you.

Flags: needinfo?(dholbert)

Until now, it's had a bunch of annotations that were inadvertantly inactive due to a typo in the test-output-matching string, and then it's got a pile of different annotations with the correctly-spelled string (but those annotations are insufficient, because we're still getting intermittent failures).

Let's just fix the typo and leave it annotated as random (passing & failing).

Attachment #9097528 - Attachment description: Bug 1583969: Simplify annotations for flaky web-platform test onhover-syncbases.html. → Bug 1583969: Simplify annotations for flaky web-platform test onhover-syncbases.html (test-annotation only)
Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b3f6625f82ab
Simplify annotations for flaky web-platform test onhover-syncbases.html (test-annotation only)
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Assignee: nobody → dholbert
You need to log in before you can comment on or make changes to this bug.