Funny thing about this: it's actually permaorange, only on Try, only on the taskcluster builds and taskcluster tests, and only if you push on top of a recent parent (which almost certainly means only if you push on top of the cset which made the taskcluster e10s tests actually do e10s). Also permaorange, mochitest-e10s-4, with test_eme_canvas_blocked.html | application timed out after 330 seconds with no output and test_peerConnection_twoVideoStreams.html | application timed out after 330 seconds with no output.

Both chunks hidden on try (which would usually mean having to hide them on every trunk tree too, but in this case since they are tier-2 and thus bustage of them doesn't call for a backout, I'm leaving the working non-try ones visible).

Do you want me to remove them until they work? This is only scheduled for try. https://treeherder.mozilla.org/#/jobs?repo=try&filter-searchStr=TC%20mochitest%20e10s&exclusion_profile=false&fromchange=77c02afb6517&group_state=expanded Not running on inbound: https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&filter-searchStr=TC%20mochitest%20e10s&exclusion_profile=false&group_state=expanded&fromchange=a674340dc97e

Heh, I completely forgot that you shut off the e10s ones elsewhere. Doesn't matter to me whether or not they run hidden, but visible permaorange on try freaks people out.

It will get fixed in bug 1227730.

https://hg.mozilla.org/integration/mozilla-inbound/rev/b406515c38b4b02736a744f3f9cec9ca54b08b11 Bug 1246019 - Disable test_alerts.html on Linux until bug 1227730 is fixed. r=kits

https://hg.mozilla.org/integration/mozilla-inbound/rev/3069836086039c06277831bd791ebc2bcce9db2c Bug 1246019 - Enable again test_alerts.html for Linux. Backout b406515c38b4. r=backout