All of the above mentioned tests are not run on Android (well mochitest-media is to some degree). Is 4 months unreasonable to fix the related tests that do not run in e10s? Is there another time frame that seems more reasonable?
On Tue, Aug 15, 2017 at 4:34 PM, Ben Kelly <bke...@mozilla.com> wrote: > On Tue, Aug 15, 2017 at 4:29 PM, <jma...@mozilla.com> wrote: > >> While there are many tests which individually are disabled or lacking >> coverage, these test suites have no non-e10s coverage: >> * web-platform-tests >> * browser-chrome >> * devtools >> * jsreftests >> * mochitest-webgl, mochitest-gpu, mochitest-media >> * reftest un-accel >> >> I would propose running these above tests on windows7-opt (we don't have >> these running yet in windows 10, although we are close), and only running >> specific tests which are not run in e10s mode, turning them off December >> 29th, 2017. >> >> Keep in mind we have had many years to get all our tests running in e10s >> mode and we have known since last year that Firefox 57 would be the first >> release that we ship e10s by default to our users- my proposal is a 4 month >> temporary measure to let test owners finish ensuring their tests are >> running in e10s mode. >> > > WPT tests do not run on android. Unless we can get WPT tests running on > android, I don't think dropping all non-e10s coverage for them is > reasonable. I don't know of any plan to move android to e10s by Dec 29. > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
