On Sun, Oct 23, 2011 at 5:30 AM, Andrea Crotti <andrea.crott...@gmail.com> wrote: > If one is not clearly defined, maybe notifying the last N developers that > committed > between the last successful builds and the failing build, would it be > possible and make sense?
Yeah, as Antoine noted, that's where we want to get to eventually, but at the moment, even the "stable" buildbots are a bit too flaky for us to turn that on (essentially, the buildbots end up spamming the alerts, so people start assuming they're *all* false alarms and the notifications become ineffective). We're getting closer though - since the buildbots were put in place, many of the flakier tests have been redesigned to be significantly more reliable. In the meantime, we rely on committers to check the buildbot pages for a day or two after they make commits to confirm there aren't any lurking cross-platforms problems or other issues with their changes. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
