Closed Bug 1410463 Opened 7 years ago Closed 7 years ago

Intermittent svg/smil/anim-marker-orient-02.svg == svg/smil/lime.svg | image comparison, max difference: 255, number of differing pixels: 400

Categories

(Core :: Graphics: WebRender, defect, P1)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla58
Tracking Flags:
Tracking Status
firefox57 --- unaffected
firefox58 --- fixed

People

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

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, Whiteboard: [wr-mvp] [stockwell unknown])

There have been 31 failures in the last 7 days. This occurs only on Linux 64-qr, on opt and debug. Here is an example of a recent log: https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-inbound&job_id=140188018&lineNumber=19491 And an example of the reftest analyzer: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/JrjqajOtQkmTmtv97rmNjA/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1 Here, I noticed that the difference is that a small red square is placed in the top left corner :milan Do you know what's causing these failures? I noticed that it's already scheduled for work on the next release. Since it's failing frequently, could it be prioritized?
Flags: needinfo?(milan)
Whiteboard: [stockwell needswork]
I guess we can just mark it random-if(webrender) again until we have cycles to investigate.
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/f584176734b9 Mark a frequent intermittent as random-if(webrender). r=me
Assignee: nobody → bugmail
Flags: needinfo?(milan)
Status: NEW → ASSIGNED
Priority: P5 → P1
Whiteboard: [stockwell needswork] → [wr-mvp] [stockwell needswork]
https://hg.mozilla.org/mozilla-central/rev/f584176734b9
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
You need to log in before you can comment on or make changes to this bug.