On Tue, Aug 8, 2017 at 5:18 PM, Ben Kelly <bke...@mozilla.com> wrote:
> On Tue, Aug 8, 2017 at 5:12 PM, <jma...@mozilla.com> wrote:
>> While we get some advantages to not running duplicated tests (faster try
>> results, less backlogs, fewer intermittent failures) there might be
>> compelling reasons to run some tests in e10s based on specific coverage.
>> With that said, I would like to say that any tests we turn on as non-e10s
>> must have a clearly marked end date- as in this is only a temporary measure
>> while we schedule work in to gain this coverage fully with e10s tests.
> If we have an android test disabled (a lot I think), then we should
> consider continuing to run the test in non-e10s on desktop linux. Having
> more real devices to run android tests on would probably reduce the number
> of tests that are disabled. The emulator is extremely slow and not
> representative of real hardware.
Sorry to self-reply, but the best solution would of course be to move
android to a single content process e10s model. Then we could truly remove
non-e10s. Obviously that is probably not easy to do, though...
dev-platform mailing list