Thank for pointing that out. In some cases we have fixed tests that are just timing out, in a few cases we disable because the test typically runs much faster (i.e. <15 seconds) and is hanging/timing out. In other cases extending the timeout doesn't help (i.e. a hang/timeout).
Please feel free to comment on any of the disabled bugs, I am happy to take another look! On Tue, Mar 7, 2017 at 12:38 PM, Marco Bonardo <mbona...@mozilla.com> wrote: > On Tue, Mar 7, 2017 at 6:34 PM, Marco Bonardo >> >> In case of mochitest browser tests failing on "This test exceeded the >> timeout threshold", the temporary solution after 1 or 2 weeks should be to >> add requestLongertimeout,rather than disabling them. They should still be >> split up into smaller tests, but doesn't make sense to disable them since >> they can complete properly. >> > > And indeed on the list you provided I see 5 of the tests are wrongly > disabled, they are not failing they just take too much time to complete. > They should be "adjusted" but still enabled and tracked by your project as > "flaky" or whatever. > > > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
