Currently, most of our e10s test automation is running on linux only; the exception is mochitest-browser-chrome which is also running on mac and windows, except windows xp. e10s is scheduled to go to beta in early Aug, and release as early as Oct; we should think about how we want to migrate tests to e10s. I think we want additional e10s tests running on win/mac fairly soon, to give devs a chance to react to issues before beta. We're likely to run into two issues doing this: 1 - builder limits problems 2 - increased wait times 1) can be mitigated via some combination of reducing chunking on twigs and omitting either e10s or non-e10s versions on twigs, depending on the purpose of the twig 2) can be mitigated by running the e10s versions periodically; at some point we'll want to switch and run the e10s versions per-commit and the non-e10s periodically. I'm not sure at what point that happens. e10s people: any thoughts on when we should start this work?

I tried all mochitests in e10s mode on Windows: https://treeherder.mozilla.org/#/jobs?repo=try&revision=6f1b17c918af You can ignore the bc/dt failures; those happened for infra reasons. mochitest-plain is in very good shape, only a couple of failures in chunk 5. The big story is that mochitest-a11y is extremely broken. I'm not sure if this is a known issue or not; we're currently not running mochitest-a11y on any platform in e10s mode. Should we be?

(In reply to Jonathan Griffin (:jgriffin) from comment #1) > I tried all mochitests in e10s mode on Windows: > https://treeherder.mozilla.org/#/jobs?repo=try&revision=6f1b17c918af Sorry, but I don't have enough context to offer any help here.

Actually a dupe of the combination of bug 1215233 and bug 1194533.