Closed Bug 1419953 Opened 2 years ago Closed 2 years ago

stylo-chrome: M-e10s(ss) on macOS may become permafailure after enabling stylo-chrome

Categories

(Core :: CSS Parsing and Computation, enhancement, P3)

enhancement

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox59 --- affected
firefox60 --- ?

People

(Reporter: xidorn, Unassigned)

References

Details

See https://treeherder.mozilla.org/#/jobs?repo=try&revision=7a406c371345e405a3df82b10f0dd2275fe78778&filter-searchStr=OS%20X%2010.10%20opt%20Mochitests%20executed%20by%20TaskCluster%20with%20e10s%20test-macosx64%2Fopt-browser-screenshots-e10s%20tc-M-e10s(ss)

It is not clear why this happens. It seems to be some timeout.

I guess we can disable it on macOS (like what was done in bug 1372833). Given the test doesn't run on autoland, I guess it is necessary to block enabling stylo-chrome.
I mean, I guess it isn't necessary to block enabling stylo-chrome.
Priority: -- → P3
Xidorn, is this bug still relevant? Is the M-e10s(ss) test perma-failing now that we've enabled Stylo-chrome in Nightly?
Flags: needinfo?(xidorn+moz)
It doesn't seem to fail on m-c at all... I think the onle place I saw it's failing was try push. So I would say it is probably not relevant given sheriffs didn't complain anything about this.
Flags: needinfo?(xidorn+moz)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.