Open Bug 1261823 Opened 4 years ago Updated 4 years ago
Dual e10s/non-e10s mode in test harnesses
Currently you can either run a test with e10s enabled, or e10s disabled, but not both. Blair McBride pointed out that maybe the default should be to run both at the same time. The upside is that people won't accidentally skip testing on one of these modes. The downside is testing locally will take twice as long (and this is coverage you'd get from try anyway). At the very least, having a mode that runs both seems worthwhile, and we can debate about whether it should be the default behaviour or not later. In the distant future I can imagine each job corresponding to a directory of tests, and within that job the tests are run in both e10s and non-e10s (assuming non-e10s is still a thing in the distant future).
You need to log in before you can comment on or make changes to this bug.