Georg Brandl <g.bra...@gmx.net> wrote: > The hard part is to know *when* to look. As you might have noticed, the > Python test suite does not run in ten seconds, especially on some of the > buildbots -- it can take 1-2 there to complete.
Based on this and other issues, I don't think it's practical to expect that people will always check that their commits pass tests on all platforms. Perhaps a slight change in culture is necessary. When someone finds a problem with a buildbot, the first response is should be to request that the committer attempt to fix the problem. Finding the guilty party can be easier said than done since there could be multiple problems or if the problem has been present for a long time. Another complication is that the commiter may not have access to the plaform and require it for debugging purposes. Basically, I think better communication could mostly solve the problem. If someone finds a test failing on a certain plaform, it's okay to complain about it. You don't have to fix it yourself. Perhaps the simpliest approach would be to open a new issue. Neil _______________________________________________ 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