High frequency [tier2] bugs/1738700-1.html == bugs/1738700-1-ref.html | image comparison, max difference: 3, number of differing pixels: 1177
Categories
(Core :: Layout, defect, P5)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | unaffected |
| firefox94 | --- | unaffected |
| firefox95 | --- | unaffected |
| firefox96 | --- | fixed |
People
(Reporter: intermittent-bug-filer, Assigned: jfkthame)
References
(Regression)
Details
(Keywords: intermittent-failure, regression)
Attachments
(2 files)
Filed by: abutkovits [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=357595845&repo=autoland
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/eLxNM-1KR_S87ntoFvASHg/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://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/eLxNM-1KR_S87ntoFvASHg/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
Comment 1•4 years ago
|
||
Jonathan, this looks to be from Bug 1738700 https://hg.mozilla.org/integration/autoland/rev/3bd4e0246b821a1239b1c184b9e5bd8a99acbf25. Could you have a look over it? It's only android-hw-p2-8-0-android-aarch64-qr so far. Thank you.
Updated•4 years ago
|
| Assignee | ||
Comment 2•4 years ago
|
||
Looks like some Android systems show more antialiasing fuzz (sigh), though I see it's not entirely consistent. With a max-difference of 3, though, it's not really a concern; we can just annotate it accordingly.
| Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 4•4 years ago
|
||
Set release status flags based on info from the regressing bug 1738700
Comment 6•4 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Comment 8•4 years ago
|
||
This is still happening: https://treeherder.mozilla.org/logviewer?job_id=357735273&repo=autoland&lineNumber=1930
Jonathan, could you take a look?
| Assignee | ||
Comment 9•4 years ago
|
||
That shows a difference on 1328 pixels instead of 1177, though still only a max-difference of 3 (insignificant). Not sure why it's so variable between different test runs, as they're all "passing" in the sense that the behavior being tested is working correctly; there's just some kind of difference between the precise antialiasing that we see. (Do all these tests always run on identical systems, or are there hardware- or driver-level differences that might affect GPU rendering, I wonder?)
Anyhow, the answer here is simply to adjust the fuzz number.
| Assignee | ||
Comment 10•4 years ago
|
||
Comment 11•4 years ago
|
||
Set release status flags based on info from the regressing bug 1738700
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
| bugherder | ||
| Comment hidden (Intermittent Failures Robot) |
Description
•