Closed Bug 1581622 Opened 5 years ago Closed 4 years ago

Intermittent svg/blend-exclusion.svg == svg/blend-exclusion-ref.svg | image comparison, max difference: 5, number of differing pixels: 254

Categories

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

defect

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox-esr68 --- unaffected
firefox76 --- unaffected
firefox77 --- unaffected
firefox78 --- fixed
firefox79 --- fixed

People

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

References

(Regression)

Details

(Keywords: intermittent-failure, regression, Whiteboard: [retriggered])

Attachments

(1 file)

Filed by: cbrindusan [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=266890604&repo=autoland
Full log: https://queue.taskcluster.net/v1/task/BkImyqLUSVSJH51Tv8Yb9A/runs/0/artifacts/public/logs/live_backing.log
Reftest URL: https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/BkImyqLUSVSJH51Tv8Yb9A/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1


[task 2019-09-16T18:45:01.306Z] 18:45:01 INFO - REFTEST TEST-START | http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion.svg == http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion-ref.svg
[task 2019-09-16T18:45:01.512Z] 18:45:01 INFO - REFTEST TEST-LOAD | http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion.svg | 1384 / 1925 (71%)
[task 2019-09-16T18:45:01.512Z] 18:45:01 INFO - REFTEST TEST-LOAD | http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion-ref.svg | 1384 / 1925 (71%)
[task 2019-09-16T18:45:01.512Z] 18:45:01 INFO - REFTEST INFO | REFTEST fuzzy test (0, 0) <= (5, 254) <= (4, 254)
[task 2019-09-16T18:45:01.512Z] 18:45:01 INFO - REFTEST TEST-UNEXPECTED-FAIL | http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion.svg == http://10.7.205.219:8854/tests/layout/reftests/svg/blend-exclusion-ref.svg | image comparison, max difference: 5, number of differing pixels: 254

Component: SVG → Graphics: WebRender
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---
Status: REOPENED → RESOLVED
Closed: 5 years ago4 years ago
Resolution: --- → INCOMPLETE
Status: RESOLVED → REOPENED
Resolution: INCOMPLETE → ---

I can't see how that change could have any effect at all. It only applies to elements that have an autofocus attribute. On top of that, this was reported 9 months ago and my fix landed 7 days ago.

Flags: needinfo?(longsonr)
Assignee: nobody → longsonr
Attachment #9152917 - Attachment description: Bug 1581622 - Suppress antialiasing in blend-exclusion reftest → Bug 1581622 - Make blend-exclusion reftest a slightly fuzzier match on geckoview webrender

Robert,
I believe Cristina was talking about the recent spike of failures that was caused by your changes.

Nevertheless a change to the code along the lines of if (element has an autofocus attribute) { do something } cannot possibly affect a testcase that doesn't have an autofocus attribute.

(In reply to Robert Longson [:longsonr] from comment #14)

Nevertheless a change to the code along the lines of if (element has an autofocus attribute) { do something } cannot possibly affect a testcase that doesn't have an autofocus attribute.

For the record: from looking at the retrigger results, I agree with the sheriffs that your commit is where this started spiking. But -- I would bet the "culprit" wasn't your code-changes, but rather the fact that you added some reftests.

Any new reftests cause reftest rebucketing, which can cause fuzzy issues to crop up in different tests (or to manifest in different ways). I don't know the exact mechanism, but it has felt like "the first test to use feature $X is susceptible to having a fuzzy pixel or two", or something to that effect. So, test-rebucketing events (caused by new reftests being added) can subtly change reftest renderings.

(Fortunately this doesn't happen every time we add a new reftest, but it does happen & it seems to be the best explanation for the facts.)

Pushed by longsonr@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/f3a829091fef
Make blend-exclusion reftest a slightly fuzzier match on geckoview webrender r=dholbert

Nice try on the explanation Daniel, but it wouldn't cover what happened in bug 1642168. There I'm supposed to have caused 3 reftests to fail and all I did to do that was make a different reftest that was already fuzzy, slightly fuzzier. No tests added or removed and no code changed. I'm hoping the whack-a-mole game is now over.

Indeed, that one seems more mysterious. Thanks for addressing both of them, in any case!

Status: REOPENED → RESOLVED
Closed: 4 years ago4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
No longer regressions: 1644404
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: