This has now landed on central. The following suites are e10s by default and require the --disable-e10s flag to run non-e10s:
* marionette * mochitest (excluding chrome, a11y and android) * reftest (excluding android) * talos * web-platform-tests I also added some logging to marionette, mochitest and reftest both at the start and end of the test run to make it easier to see whether e10s was enabled or not (ctrl-f for e10s). Please file bugs blocking bug 1243083 if you believe something is amiss. Finally, bug 1261823 was filed to investigate a dual-mode that runs both e10s and non-e10s. There is no eta at this time. -Andrew On 24/03/16 12:15 PM, Andrew Halberstadt wrote:
Bug 1243083 tracks enabling e10s by default when running tests locally. I intend to do this for as many harnesses as possible unless someone says otherwise. The implication is that the --e10s flag will be renamed to --disable-e10s. So you'll need to pass in --disable-e10s if you wish to run without e10s enabled. This also means that tests that are skipped with 'e10s' will no longer run by default locally. The hope is that this will make it easier for devs to find and fix tests that are broken with e10s enabled, as well as ensure that new tests work with e10s right out of the gate. CI jobs will not be affected, only running locally. One potential sticking point is mochitest-chrome. It currently does not get run in e10s in CI, so local configuration should mirror this. However, since --e10s is being removed, this means it would be impossible to run mochitest-chrome in e10s without modifying source files. Maybe this just needs some argparse hackery. If you have any concerns or know of other suites that should explicitly *not* be run with e10s enabled by default, please let me know. Andrew
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
