It might be a good idea to integrate this process with the OrangeFactor Robot, to avoid race conditions like what happened on bug 1328486 (it was bulk-closed, and then a couple of hours later the OF robot reported that there were two failures this week - but the bug remained closed).
Cheers, kats On Fri, Jul 7, 2017 at 10:35 PM, Emma Humphries <e...@mozilla.com> wrote: > As discussed earlier, Joel and I have kicked off a process to close > intermittent test failures in Bugzilla. > > If a test associated with a bug does not fail in 21 days, we'll close the > bug as RESOLVED:INCOMPLETE. > > The first batch of intermittent bugs to close has 5,130 tickets. I have a > script to close these, but to close these without bug spam requires DBA > intervention. > > I'd like to run the closures over the weekend but that's going to create a > non-trivial amount of bug spam for some of you. > > There is a way to get rid of the bug spam! > > Every bug we close will have the keyword `bulk-close-intermittents` added > to it. > > If you search for messages from `bugzilla-dae...@mozilla.org` containing > `bulk-close-intermittents` you can isolate, review, and remove those > messages. > > Thank you for your patience while we all work to get the noise out of > Bugzilla so we can find the strong signals on what we must focus on to > deliver Firefox 57 in November. > > -- Emma > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
