On Tuesday, August 19, 2014 11:46:08 AM UTC-4, Gavin Sharp wrote: > > 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
Bug 1041569 - has been needinfo'd for 4 weeks, it is only disabling this on win debug, I don't know how to reduce that anymore, especially if nobody wants to look at it. bug 1041583 - no activity in 4+ week as well. We are only disabling it on windows debug bug 1017187 - no reply in 4+ weeks, this is disabling the test on all debug branches. bug 1001820 - idle for 3 weeks until last week and it was recommended to disable the test (in fact it appears to be disabled) bug 963075 - no activity for 4 weeks, we need to disable 2 pdf tests on opt builds only. All in all we are changing 12 tests in the manifests. It is obvious based on the lack of response in the bugs that fixing these bugs are not a priority, changing the way we run these tests will only give us more reliable results and less churn when we need to adjust chunking or jobs. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
