[Python-Dev] Looking after the buildbots (in general) (original) (raw)

Georg Brandl g.brandl at gmx.net
Wed Aug 4 23:53:22 CEST 2010

Am 04.08.2010 17:53, schrieb Georg Brandl:

Am 04.08.2010 17:15, schrieb exarkun at twistedmatrix.com:

On 02:51 pm, barry at python.org wrote:

On Aug 04, 2010, at 11:16 AM, Antoine Pitrou wrote:

I think the issue is that many core developers don't have the reflex to check buildbot state after they commit some changes (or at least on a regular, say weekly, basis), and so gradually the buildbots have a tendency to turn from green to red, one after another.

I'd classify this as a failure of the tools, not of the developers. These post-commit verification steps should be proactive, and scream really loud (or even prevent future commits) until everything is green again. Buildbots themselves can be unstable, so this may or may not be workable, and changing any of this will take valuable volunteer time. It's also unsexy work. How hard is it to look at a web page? 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.

That should be "1-2 hours", by the way...

Georg

-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list