zope-tests - FAILED: 14, OK: 17, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2013-02-21 00:00:00 UTC and 2013-02-22 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] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux [3] Still Failing - zopetoolkit_trunk - Build # 181 [4] Still Failing - zopetoolkit_trunk_app - Build # 163 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5] winbot / z3c.authenticator_py_265_32 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.jsonrpc_py_265_32 [8] winbot / z3c.jsontree_py_265_32 [9] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.tabular_py_265_32 [11] winbot / zope.app.appsetup_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.generations_py_265_32 [14] winbot / zope.app.wsgi_py_265_32 [15] winbot / zope.browsermenu_py_265_32 [16] winbot / zope.browserpage_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] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072705.html [2] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072706.html [3] FAILED Still Failing - zopetoolkit_trunk - Build # 181 https://mail.zope.org/pipermail/zope-tests/2013-February/072698.html [4] FAILED Still Failing - zopetoolkit_trunk_app - Build # 163 https://mail.zope.org/pipermail/zope-tests/2013-February/072699.html [5] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072722.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072720.html [7] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072696.html [8] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072697.html [9] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072726.html [10] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072719.html [11] FAILED winbot / zope.app.appsetup_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072723.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072694.html [13] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072695.html [14] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072724.html [15] FAILED winbot / zope.browsermenu_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072725.html [16] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072721.html
On Sat, Feb 23, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux
Same old.
[3] Still Failing - zopetoolkit_trunk - Build # 181 [4] Still Failing - zopetoolkit_trunk_app - Build # 163
IOError: [Errno 2] No such file or directory: '/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.app.wsgi/setup.py' Probably another "moved to Github"
[5] winbot / z3c.authenticator_py_265_32
Same (unicode password became str)
[6] winbot / z3c.contents_py_265_32
Same (I still can't reproduce)
[7] winbot / z3c.jsonrpc_py_265_32
New: File "c:\buildslave\z3c.jsonrpc\build\src\z3c\jsonrpc\tests\..\README.txt", line 270, in README.txt Failed example: proxy.hello() Exception raised: Traceback (most recent call last): File "c:\Python26_32\lib\doctest.py", line 1253, in __run compileflags, 1) in test.globs File "<doctest README.txt[49]>", line 1, in <module> proxy.hello() File "c:\eggs\z3c.json-0.5.4-py2.6.egg\z3c\json\proxy.py", line 93, in __call__ return self.call(data) File "c:\eggs\z3c.json-0.5.4-py2.6.egg\z3c\json\proxy.py", line 153, in __request raise ResponseError("Invalid request id returned") ResponseError: Invalid request id returned I've no idea.
[8] winbot / z3c.jsontree_py_265_32
Same as above.
[9] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.tabular_py_265_32
Same old (I can't reproduce)
[11] winbot / zope.app.appsetup_py_265_32
Moved to github
[12] winbot / zope.app.authentication_py_265_32
Principal ID expected to be str, turns out to be unicode.
[13] winbot / zope.app.generations_py_265_32
All tests pass in latest build.
[14] winbot / zope.app.wsgi_py_265_32 [15] winbot / zope.browsermenu_py_265_32 [16] winbot / zope.browserpage_py_265_32
Moved to github. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer