This is the summary for test reports received on the zope-tests list between 2014-01-23 00:00:00 UTC and 2014-01-24 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Successful - zopetoolkit_trunk - Build # 524 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / zope.testbrowser_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080601.html
On Sat, Jan 25, 2014 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080601.html
No changes in zope.testbrowser, but a new failure. I'm guessing API change in some upstream library, probably WebTest. Locally I'm seeing more failures than winbot reports. But then again locally I just discovered a modified copy of wsgiref/simple_server.py with an 'import pdb; pdb.set_trace()' in it, so I'm not trusting this old sandbox. Maybe it's just that winbot runs the tests with -1, and tox doesn't. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer