Open
Bug 1255095
Opened 9 years ago
Updated 3 years ago
Make mochitest chrome produce an error when run with --e10s
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(e10s+)
NEW
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: mccr8, Unassigned)
References
(Blocks 1 open bug)
Details
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.
Reporter | ||
Updated•9 years ago
|
tracking-e10s:
--- → ?
Comment 1•9 years ago
|
||
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?
Comment 2•9 years ago
|
||
(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.
Comment 3•9 years ago
|
||
Yep, thanks for fixing that!
Updated•9 years ago
|
Blocks: e10s-tests
Comment 4•9 years ago
|
||
Bug 1243083 will replace --e10s with --disable-e10s. Will that be a good enough alternative to an error message?
Comment 5•9 years ago
|
||
I think that makes the situation even more confusing.
Assignee | ||
Updated•7 years ago
|
Component: Mochitest Chrome → Mochitest
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•