> Does anyone have any suggestions?
I guess that's a buildbot bug. At 2009-11-23 22:14:23, your
buildslave disconnected. The master recognized it it as offline.
For some reason, it then still decided to start a build, at
22:14:24. With the slave disconnected, all master-side information
gets disca
Paul Moore writes:
> Hmm, wasn't me :-) The reason field on the build is blank, so this
> looks like it's an automatic build.
If it's got an SVN tag indicated, and you can checkout that tag on
your slave, then it's probably not the scenario that I was thinking
of.
In my case, it's almost always
Paul Moore gmail.com> writes:
>
> I'm getting odd failures with some of the tests as well, at the moment
> - test_smtplib and others failing but when "Re-running failed tests in
> verbose mode" there were no failures.
>
> I wonder if it could be a flaky network connection...?
test_smtplib is no
2009/11/24 David Bolen :
> Paul Moore writes:
>
>> buildbot.interfaces.BuildSlaveTooOldError: This buildslave
>> (moore-windows) does not know about multiple branches, and using
>> mode=update would probably build the wrong tree. Refusing to build.
>> Please upgrade the buildslave to buildbot-0.7.
Paul Moore writes:
> buildbot.interfaces.BuildSlaveTooOldError: This buildslave
> (moore-windows) does not know about multiple branches, and using
> mode=update would probably build the wrong tree. Refusing to build.
> Please upgrade the buildslave to buildbot-0.7.0 or newer.
>
> This is very odd
I'm getting occasional odd errors in the subversion step on my
buildslave (http://www.python.org/dev/buildbot/buildslaves/moore-windows):
Traceback (most recent call last):
File "/data/buildbot/lib/python/buildbot/process/buildstep.py", line
690, in startStep
d.addCallback(self._startStep_2)
