[Distutils] [buildout] windows/jenkins annoyance

Chris Withers chris at simplistix.co.uk
Sat Jan 19 22:51:32 CET 2013

On 19/01/2013 21:16, Jim Fulton wrote:
>> 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?
> No, can you? :)
> The problem is that buildout is upgrading for a new setuptools. To do this,
> it needs to rewrite the buildout script, but *windows* won't let it do that
> because the script is open.  Maybe there's a better way around this.

Can you point me at the buildout code?

> Your workaround, if I understand it, to wait 20 seconds looks good to me. :)

...except the spurious failures :-(

> Another option would be to pin setuptools in your buildout.cfg to avoid the
> upgrade.

Would that work? How would I pin to a version of distribute?

>> PS: Where does the buildout continuous integration testing live nowadays?
> https://travis-ci.org/buildout/buildout

Hmm, I don't even know how to read that I'm afraid :-S

> http://winbot.zope.org/builders/
> Note that the buildout 1 tests always fail. (I give up.)

I spy some 1.6.x tests, I thought the "1" branch was on 1.7 now?
If those are the tests you're referring to, they appear to be failing on 
the git part, rather than anything further...

Where can I find out how I should be looking to run the tests?



Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk

More information about the Distutils-SIG mailing list