Closed
Bug 1264056
Opened 9 years ago
Closed 8 years ago
Intermittent REFTEST TEST-UNEXPECTED-FAIL | grid-fragmentation-002.html | image comparison (==), max difference: 255, number of differing pixels: 9533
Categories
(Core :: Layout: Block and Inline, defect, P4)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox52 | --- | unaffected |
firefox-esr52 | --- | unaffected |
firefox53 | --- | fixed |
firefox54 | --- | fixed |
firefox55 | --- | fixed |
People
(Reporter: reznord, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [fixed by bug 1317149][stockwell disabled])
REFTEST TEST-UNEXPECTED-FAIL | file:///home/worker/workspace/build/tests/reftest/tests/layout/reftests/css-grid/grid-fragmentation-002.html | image comparison (==), max difference: 255, number of differing pixels: 9533
Treeherder Link: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&selectedJob=25636887
Updated•9 years ago
|
Component: JavaScript: Internationalization API → Layout: Block and Inline
Comment 1•9 years ago
|
||
The Treeherder link above gives me an error message: "Selected job id: 25636887 not within current result set range. Load result set".
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 2•9 years ago
|
||
Oh, I should also click "load result set".
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 3•9 years ago
|
||
layout/reftests/css-grid/grid-fragmentation-002.html is testing fragmentation of
grid-aligned abs.pos. children. I'm not surprised this test failed since our
support for fragmentating abs.pos. is somewhat flaky in general (not just in Grid).
Severity: normal → minor
Priority: -- → P4
Comment 4•9 years ago
|
||
This becomes almost a permafail with my patchset for bug 1261279... not sure why
https://treeherder.mozilla.org/#/jobs?repo=try&revision=4586dcdd79dc
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 11•8 years ago
|
||
This has been a low-frequency failure on Windows and Linux for a few months. There was a significant spike in failures, all on Android, beginning Feb 12. I don't see many failures today though, so this might not be an issue...will check back in a day or so...
Flags: needinfo?(gbrown)
Comment 12•8 years ago
|
||
Seems to be back to low frequency, desktop and Android now.
Flags: needinfo?(gbrown)
Comment hidden (Intermittent Failures Robot) |
Comment 14•8 years ago
|
||
and back to high frequency
Comment hidden (Intermittent Failures Robot) |
Updated•8 years ago
|
Whiteboard: [stockwell unknown]
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment 18•8 years ago
|
||
this picked up quite a bit, specifically on android debug reftest-26 :)
I am doing some retriggers here:
https://treeherder.mozilla.org/#/jobs?repo=autoland&filter-searchStr=android%20debug%20reftest-26&tochange=45dc8c1db2792025efa14127d56626fd5c6f419a&fromchange=6c8cf852db30215ea93b6f63de157a00ec3f6020&selectedJob=82457518
we had a stylo reftest regression in the same window, this shouldn't be related, but... who knows :)
Updated•8 years ago
|
Whiteboard: [stockwell unknown] → [stockwell needswork]
Comment 19•8 years ago
|
||
I'm wallpapering this by commenting out the part of the test that fails, in bug 1317149.
Comment 20•8 years ago
|
||
Should be fixed by bug 1317149 now.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
Depends on: 1317149
Resolution: --- → FIXED
Whiteboard: [stockwell needswork] → [fixed by bug 1317149]
Updated•8 years ago
|
Whiteboard: [fixed by bug 1317149] → [fixed by bug 1317149][stockwell disabled]
Comment hidden (Intermittent Failures Robot) |
Updated•8 years ago
|
status-firefox52:
--- → unaffected
status-firefox53:
--- → fixed
status-firefox54:
--- → fixed
status-firefox55:
--- → fixed
status-firefox-esr52:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•