On Wed, Aug 4, 2010 at 7:42 PM, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: > On Wed, Aug 4, 2010 at 11:16, Antoine Pitrou <solip...@pitrou.net> wrote: >> I would advocate a system were people are encouraged to take >> responsibility of the problems they introduce when committing changes. >> Of course, there are sometimes situations where it's not possible >> (triggering platform-specific oddities, for example). > > They might not be able to diagnose the problems, or fix them, but I > think they should still take responsibility until handed over > explicitly to someone else who knows the failing platform, right? > > It should be relatively straightforward to have some process send > email to authors of checkins that have created new failures.
I believe that was the original intent, but the buildbot set generated too many false alarms (due to flaky tests which would fail intermittently) so it was never implemented. However, I believe the 3.x tests have had most of that flakiness eliminated (dropping bsddb helped greatly on that front), so it should be feasible to restore that feature for the stable buildbot set on the Py3k branch. 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
