Disabling a few mochitests this week, and upcoming changes next week to browser-chrome

Gavin Sharp gavin at gavinsharp.com
Tue Aug 19 19:08:08 UTC 2014

On Tue, Aug 19, 2014 at 9:06 AM, Ed Morley <emorley at mozilla.com> wrote:
> Agreed that this case is possibly slightly different - however this change
> is merely exposing already flaky tests - and this change is very much
> overdue. If the tests mentioned are really that important, then could we
> please get people allocated to fixing them?

We have allocated people to fixing them. These bugs were explicitly
assigned in the 34.2 iteration:
Bug 947574
Bug 1002439
Bug 1041537

and we've made some significant progress in tracking them down. But as
you know, fixing these issues can be relatively difficult.

> Ultimately no one individual test should have the right to destroy the SnR
> for a suite - and if we don't have this policy as a rapid (and enforceable
> in practice) means to control rogue tests, then the only other hammer the
> sheriffs have is to hide entire suites.

If we're reduced to interacting with each other with hammers, then
we've failed. Firefox peers will not ignore needinfo or review
requests. If you feel that they are, then you can escalate to me as
module owner. I do not ignore requests, and am quite responsive to
email and IRC pings.


More information about the firefox-dev mailing list