Closed
Bug 1430572
Opened 7 years ago
Closed 7 years ago
Intermittent reftest failures due to failure to load/use the expected font [was: Intermittent race between taking the reftest and loading the WOFF]
Categories
(Core :: Graphics, defect, P3)
Core
Graphics
Tracking
()
RESOLVED
FIXED
People
(Reporter: aryx, Unassigned)
References
Details
(Keywords: intermittent-failure, Whiteboard: [gfx-noted][PI:March])
+++ This bug was initially created as a clone of Bug #1396260 +++
https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&revision=4c230b89e05e6a4d87d3f26e2ca862dd59e617d0&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable has two 2 reftest failures which looks similar to bug 139620 which got fixed for firefox 57.
See the failures in 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/eG9n-65xT1uJxy6-lHSIRQ/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
https://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/T17ICTEOTkK_HW_8Qq2V2w/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1
Comment 1•7 years ago
|
||
(In reply to Sebastian Hengst [:aryx][:archaeopteryx] (needinfo on intermittent or backout) from comment #0)
> +++ This bug was initially created as a clone of Bug #1396260 +++
>
> https://treeherder.mozilla.org/#/jobs?repo=mozilla-
> release&revision=4c230b89e05e6a4d87d3f26e2ca862dd59e617d0&filter-
> resultStatus=testfailed&filter-resultStatus=busted&filter-
> resultStatus=exception&filter-resultStatus=retry&filter-
> resultStatus=usercancel&filter-resultStatus=runnable has two 2 reftest
> failures which looks similar to bug 139620 which got fixed for firefox 57.
I think the issue here is that bug 1396260 was not really "fixed" at all; the patch there made us run reftests in more (smaller) chunks on Win7, which substantially reduced the frequency of these failures, but the underlying problem (which looks like some kind of failure in Gfx, perhaps related to resource exhaustion) hasn't changed.
Comment 2•7 years ago
|
||
I currently believe this is a Graphics issue rather than Layout/CSS, fwiw.
Component: CSS Parsing and Computation → Graphics
| Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted]
| Comment hidden (Intermittent Failures Robot) |
I am considering removing the "hyper-chunking" solution and pulling the fonts out into their own job- most likely that will fail a lot, but we can move that to tier-2 until the graphics issue is resolved.
See Also: → 1396260
Comment 6•7 years ago
|
||
(In reply to Joel Maher ( :jmaher) (UTC-5) from comment #5)
> I am considering removing the "hyper-chunking" solution and pulling the
> fonts out into their own job- most likely that will fail a lot, but we can
> move that to tier-2 until the graphics issue is resolved.
+1
Whiteboard: [gfx-noted] → [gfx-noted][PI:February]
it looks like we still have the same volume of font based failures- I want to:
1) shrink back to <=8 chunks of reftests
2) move font reftests to their own job and mark as tier-2 or 3 to remove the failures we are seeing
Whiteboard: [gfx-noted][PI:February] → [gfx-noted][PI:March]
with running tests by manifest as well as reducing the chunks (2 opt/pgo, 4 debug), I consider this bug not useful to keep around. We still have a lot of font failures on win7 reftests; that rate of failure hasn't changed at all. If we decide this is still too much to work with, I will create a new bug and move font-face reftests to their own job as tier2 or tier3.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•