This is the summary for test reports received on the zope-tests list between 2014-01-06 00:00:00 UTC and 2014-01-07 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 ---------------- [1] Failure - zopetoolkit_trunk - Build # 507 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / zc.table_py_265_32 [3] winbot / zope.container_py_265_32 [4] winbot / zope.security_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 Failure - zopetoolkit_trunk - Build # 507 https://mail.zope.org/pipermail/zope-tests/2014-January/080372.html [2] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080370.html [3] FAILED winbot / zope.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080369.html [4] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080371.html
On Wed, Jan 08, 2014 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] Failure - zopetoolkit_trunk - Build # 507 [2] winbot / zc.table_py_265_32 [3] winbot / zope.container_py_265_32
All fixed already by Adam.
[4] winbot / zope.security_py_265_32
Same uppercase/lowercase hex comparison failure. Since zope.security hasn't changed in 6 months, maybe one of its dependencies did? zope.proxy perhaps? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer