The backout was done based on the suggestion that the Dev made: https://bugzilla.mozilla.org/show_bug.cgi?id=1186965#c9
The dev was well aware of the crash it caused as well as the tests he could have backed out of. Should I have backed out of his tests for that as well? Based on this information, it sounds like I should have. It doesn't make sense to me why a dev knowing that a crash happens doesn't try to fix the crash before landing the whole thing. I understand not wanting to hide an issue, but to not resolve the issue and then have other people on nightly suffer as well doesn't make sense to me. On Sun, Jul 26, 2015 at 11:32 PM, Carsten Book <cb...@mozilla.com> wrote: > Hi, > > just as little reminder. > > Please be careful with backouts. > > We had a issue on friday when a backout was incomplete (like from 2 > checkins landed from a bug only one backed out) and so this broke break W3 > test on all platforms where MSE was enabled (win >= 7 and OSX) on > mozilla-central. So this caused more issues for the Mozilla-Central Tree > and so not just b2g. (also seems the original code in this case was > innocent and so relanded); > > Cheers, > > - Tomcat > > > On Fri, Jul 24, 2015 at 8:58 PM, Jonas Sicking <jo...@sicking.cc> wrote: > >> On Fri, Jul 24, 2015 at 8:58 AM, Naoki Hirata <nhir...@mozilla.com> >> wrote: >> > Also does anyone have any objections to backing out immediately? >> >> Not at all. >> >> I fully agree with Dietrich and Kyle. >> >> / Jonas >> _______________________________________________ >> dev-gaia mailing list >> dev-g...@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-gaia >> > >
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
