On Thu, Feb 27, 2014 at 10:28:14PM -0500, Tres Seaver wrote:
On 02/27/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-February/081112.html
[2] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-February/081110.html
[3] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-February/081111.html
All three are failures to install lxml 3.3.x:
lxml 3.3.2 was released just the other day. wineggbuilder is not building wineggs for it because Windows: exceptions.WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\buildslave\\wineggbuilder\\build\\.git\\objects\\pack\\tmp_pack_OzdySd' -- http://winbot.zope.org/builders/wineggbuilder/builds/49251/steps/git/logs/st... The same error during "git" step shows up for all the builds shown on http://winbot.zope.org/builders/wineggbuilder/ If I look at the Task Manager over rdesktop, I see a bunch of git.exe and one git-remote-https.exe process belonging to user buildbot. I don't see a way to see the command line, or timestamp when a process was started. My Windows-fu is lacking. I'll try killing the git-remote-https.exe process and see if that unblocks wineggbuilder.
------------------------------- %< ---------------------------------- Getting distribution for 'lxml'. Building lxml version 3.3.2. ... Error: Couldn't install: lxml 3.3.2 ------------------------------- %< ----------------------------------
except that the z3c.contetnts failure is tied to lxml 3.3.0 instead of 3.3.2.
That's weird. 3.3.0 and 3.3.2 do not have windows binary packages on PyPI. 3.3.1 has windows binary packages on PyPI. The build succeeded a couple of days ago, which means it was using 3.3.1 back then. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development