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

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


> Going with our test disabling policy (https://wiki.mozilla.org/Sheriffing/Test_Disabling_Policy), I am going to get ready and disable tests on Friday.

A few issues here:
- This particular case (we're making broad changes to how the tests
run that causes many new failures) was not what that policy was meant
to cover. We need some leeway to handle this situation differently.
- This policy should probably clarify that any test disabling patches
still require module owner/peer review.

> You can see all the bugs that are blocking bug 992911 (https://bugzilla.mozilla.org/showdependencytree.cgi?id=992911&hide_resolved=1)

We cannot disable all of the tests in that list wholesale. At least
bug 1041569, bug 1041583, bug 1017187, bug 1001820, and bug 963075
need alternate solutions (i.e. more targeted disabling or fixes).

Gavin

On Tue, Aug 19, 2014 at 7:07 AM, jmaher <joel.maher at gmail.com> wrote:
> It has been 3+ weeks since Vaibhav and I found the remaining issues with --run-by-dir (https://bugzilla.mozilla.org/show_bug.cgi?id=992911) for browser-chrome.  Since then a few issues have been fixed, and many have been ignored.
>
> Going with our test disabling policy (https://wiki.mozilla.org/Sheriffing/Test_Disabling_Policy), I am going to get ready and disable tests on Friday.  This weekend I can sort out any remaining issues (there are always new issues that show up as the product changes) and turn on --run-by-dir next week.
>
> You can see all the bugs that are blocking bug 992911 (https://bugzilla.mozilla.org/showdependencytree.cgi?id=992911&hide_resolved=1)
>
> Happy hacking,
> -jmaher
> _______________________________________________
> dev-platform mailing list
> dev-platform at lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform



More information about the firefox-dev mailing list