[buildout] windows issue causes jenkins problems
Hi All,
The weird process forking stuff that running buildout on windows sometimes does causes problems for Jenkins:
http://jenkins.simplistix.co.uk/job/testfixtures-buildout/32/PYTHON=2.6,labe...
Is there any way I can cause this not to happen?
cheers,
Chris
On Sun, Jan 8, 2012 at 8:29 AM, Chris Withers chris@simplistix.co.uk wrote:
Hi All,
The weird process forking stuff that running buildout on windows sometimes does causes problems for Jenkins:
http://jenkins.simplistix.co.uk/job/testfixtures-buildout/32/PYTHON=2.6,labe...
Is there any way I can cause this not to happen?
I don't remember the details and I don't have time to look right now, but it has something to do with Windows not letting you remove or move open files.
You could try coming up with an alternate bootstrap that takes a different approach.
Another idea is to keep a buildout to the side and use that to bootstrap the buildouts your doing while testing.
Jim
Olivier,
ShiningPanda plugin 0.7 looks fantastic. Sadly, for at least one of the things I wanted to use it for there's a snag:
On 08/01/2012 13:29, Chris Withers wrote:
The weird process forking stuff that running buildout on windows sometimes does causes problems for Jenkins:
http://jenkins.simplistix.co.uk/job/testfixtures-buildout/32/PYTHON=2.6,labe...
Is there any way I can cause this not to happen?
I had an outside hope that ShiningPanda would somehow wait for the weird forking stuff to be done, but sadly not:
http://jenkins.simplistix.co.uk/job/testfixtures-buildout/PYTHON=2.5,label=w...
So, for now I'll have to stick with the hacky script:
https://github.com/Simplistix/testfixtures/blob/master/jenkins.bat
Any ideas on this? (other than rewriting buildout not to do the silly forking ;-) )
cheers,
Chris
participants (2)
-
Chris Withers -
Jim Fulton