![](https://secure.gravatar.com/avatar/276928028a2075ceeb0b7aface8e2e2a.jpg?s=120&d=mm&r=g)
Hi Jim, This is an example of the Windows problem I was referring to: http://jenkins.simplistix.co.uk/job/testfixtures-buildout/160/PYTHON=2.5,lab... C:\Python25\python.exe bootstrap.py ...appears to fork off a process in such a way that it returns instantly and then runs in the background. Of course, Jenkins has no way to know how long to wait for, so problems such as those above occur. My horrible hack around this is: https://github.com/Simplistix/testfixtures/blob/master/jenkins.bat#L2 ...which waits 20 seconds and then moves to the next step. It's far from reliable, especially when the Windows box has any load on it. Can you make any suggestions how to solve this problem? cheers, Chris PS: Where does the buildout continuous integration testing live nowadays? -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk