On 01:28 am, db3l....@gmail.com wrote:
exar...@twistedmatrix.com writes:
This sounds like something that should be reported
upstream. Particularly if you know how to reproduce it. Has it been?
No, largely because I can't reproduce it at all. It's happened maybe
4-5 times in the past 2 years or so. All that I see is that my end
looks good yet the master end seems not to be dispatching jobs (it
never shows an explicit disconnect for my slave though).
My best guess is that something disrupted the TCP connection, and that
the slave isn't doing anything that would let it know its connection
was dropped. Although I thought there were periodic pings even from
the slave side.
Given the frequency, it's not quite high priority to me, though having
the master let the owner of a slave know when it's down would help cut
down on lost availability due to this case, so I suppose I could
suggest
that feature to the buildbot developers.
This feature exists, at least. BuildBot can email people when slaves
are offline for more than some configured time limit. I'm not sure if
the CPython master is configured to do this or not.
It's easy to set up if not, the BuildSlave initializer accepts a list of
email addresses that will be notified when that slave goes offline,
notify_on_missing:
http://buildbot.net/apidocs/buildbot.buildslave.AbstractBuildSlave-
class.html#__init__
Jean-Paul
_______________________________________________
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
