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

[Georg Brandl]

Am 04.08.2010 18:21, schrieb David Stanek:
> On Wed, Aug 4, 2010 at 11:53 AM, Georg Brandl <g.brandl at 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.  So if you look too soon,
>> you won't see all the results, and usually the slow systems are the
>> interesting ones.
>>
>> Now we could of course have a commit hook that counts down two hours and
>> then sends an email to the committer "Now look at the buildbot!"...
>>
> 
> Why not have buildbot slaves email the committer when their change
> broke the build. I realize that if you break 25 slaves it would not be
> pleasant to receive 25 emails, but I've had worse things happen. Or
> buildbot slaves can report failures to a mailing list or IRC chat.

This is what we did once (or the mails were sent to python-dev, I don't
remember), but it became ugly fast whenever the buildbots became unstable.
Also, some of the buildbot slave owners do not have endless spare time
to look at issues on their side.

Once we manage to get them into a mostly stable situation again, we
should definitely enable notifications in on form or other again.

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.