On Thu, Apr 04, 2013 at 01:46:00PM -0400, Tres Seaver wrote:
On 04/03/2013 09:00 PM, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 222 https://mail.zope.org/pipermail/zope-tests/2013-April/073673.html
Ugh. I think Marius had some clue to this one, but I'm baffled.
I suspected https://bugs.launchpad.net/zc.buildout/+bug/257555 IIRC BTrees setup_requires=['persistent'] in setup.py. When mr.developer instructs buildout to develop BTrees, setuptools end up downloading persistent-*.egg in the source directory, outside buildout's jurisdiction, and then, somehow, buildout assumes that persistent is installed system-wide and doesn't add the persistent egg to the sys.path of the generated bin/test-ztk-whatever script. That's just a guess, I haven't spent any appreciable time debugging this.
[2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073684.html
[3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073685.html
[4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073686.html
[5] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073687.html
Looks like more renormalizer fun.
Yes. I think I got it this time. But I thought so the previous two times too. ;-)
[8] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073675.html
Network failure during 'git pull'.
Last zope.security build was successful. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development