[Buildbot-devel] Perplexing issue on Windows

Daniel e_list1 at earthlink.net
Wed Jul 30 19:19:36 UTC 2008

Greetings, all.

I have a new build slave that I have never been able to get to work.   
I am moving a buildbot slave from one Windows XP 64-bit system to  
another, and the new slave locks up every time it tries to build  
something.  Specifically what happens is: one build might work (or it  
might not), but subsequent builds always (yes, always) fail.  There  
are 2 builds on this slave, and both fail with the same two problems.

The first time they fail it is always due to a 1200-second timeout,  
with an error that buildbot could not kill processes.  Every  
subsequent failure (that is, every failure prior to my restarting the  
buildbot slave on that system) is an OS error that a specific file  
could not be removed.  If I check with procexp, I can see that named  
the file is still in use by a running shell process.  However, even if  
I kill that process, the build does not complete.  The only solution I  
have found is to quit Cygwin, which sometimes takes a reboot, since at  
that point Cygwin is usually hung and often refuses to die.

The builds still (and always) run fine on the original slave system.   
All of my other build slaves (Linux and OS X) are without issue.

I was running 0.7.7 but have upgraded to 0.7.8 and I see the same  
results on that version.  I am running buildbot in Cygwin on XP 64-bit.

I would appreciate any guidance you can provide on how to figure out  
what's going on here, and how to get past it.



More information about the devel mailing list