Over and over again I see people running mochitest chrome tests with --e10s, and when they see that it works, they assume things are working with e10s, when in fact as far as I am aware the flag is just ignored. (The latest is bug 1254806 comment 32.) The test harness should really produce an error so people aren't misled.
https://wiki.mozilla.org/Electrolysis/e10s_test_tips#Browser-chrome says "You can run a mochitest-chrome test in a multi-process environment with: mach mochitest --e10s <testname>" I guess s/mochitest-chrome/browser-chrome/ is intended there?
(In reply to Karl Tomlinson (ni?:karlt) from comment #1) > I guess s/mochitest-chrome/browser-chrome/ is intended there? I made that change to the wiki.
Yep, thanks for fixing that!
Bug 1243083 will replace --e10s with --disable-e10s. Will that be a good enough alternative to an error message?
I think that makes the situation even more confusing.
Component: Mochitest Chrome → Mochitest
You need to log in before you can comment on or make changes to this bug.