On Thu, Mar 07, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 193 https://mail.zope.org/pipermail/zope-tests/2013-March/073094.html
The usual ./bin/buildout -t 3 -v -c development-python.cfg failing because there's no development-python.cfg in SVN. There's a development-python2.cfg (rather new, added 3 days ago) and a development.cfg (which is older). Typo in the Jenkins job build steps?
[2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.formui_py_265_32 [6] winbot / z3c.pagelet_py_265_32 [5] winbot / z3c.layer.ready2go_py_265_32
lxml
[4] winbot / z3c.language.switch_py_265_32
Latest build is green!
[7] winbot / zc.resourcelibrary_py_265_32
The usual weirdness with WindowsError.
[8] winbot / zope.app.http_py_265_32
Hm, HEAD is now at 9df6d04 Pin zope.app.wsgi to <4.0dev to avoid test failures and then a failure in File "c:\eggs\zope.app.wsgi-4.0.0a3-py2.6.egg\zope\app\wsgi\testlayer.py", line 21, in <module> so the pin didn't take effect. Huh? I see bin/buildout is version 1.7 on buildout, despite my replacing of bootstrap.py with the latest http://downloads.buildout.org/2/bootstrap.py. Why? The same fix worked for zope.app.publication somehow. Despite it also using zc.buildout 1.7, despite my latest bootstrap. Or did it? Nope, but that build happened four minutes after midnight and didn't make it into this build summary. Oh, right, the bootstrap step is c:\Python26_32\python.exe c:\buildmaster\bootstrap.py everything is clear now. (Including the fact that most packages I try to build locally fail because their bootstrap is too old. I was wondering why they didn't fail en-masse on winbot.)
[9] winbot / zope.app.pagetemplate_py_265_32 [11] winbot / zope.browserpage_py_265_32
\r\n
[10] winbot / zope.app.renderer_py_265_32
Renamed to zope.renderer. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development