zope-tests - FAILED: 23, OK: 20
This is the summary for test reports received on the zope-tests list between 2013-02-17 00:00:00 UTC and 2013-02-18 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] Still Failing - zopetoolkit_trunk - Build # 177 [2] Still Failing - zopetoolkit_trunk_app - Build # 159 [3] Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux 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 Zope-trunk Python-2.6.8 : Linux Zope-trunk 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 [4] winbot / z3c.configurator_py_265_32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.jsonrpc_py_265_32 [7] winbot / z3c.jsontree_py_265_32 [8] winbot / z3c.language.switch_py_265_32 [9] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.menu.ready2go_py_265_32 [11] winbot / z3c.password_py_265_32 [12] winbot / z3c.table_py_265_32 [13] winbot / z3c.tabular_py_265_32 [14] winbot / zc.sourcefactory_py_265_32 [15] winbot / zope.app.applicationcontrol_py_265_32 [16] winbot / zope.app.form_py_265_32 [17] winbot / zope.app.generations_py_265_32 [18] winbot / zope.app.renderer_py_265_32 [19] winbot / zope.app.rotterdam_py_265_32 [20] winbot / zope.app.security_py_265_32 [21] winbot / zope.app.server_py_265_32 [22] winbot / zope.formlib_py_265_32 [23] 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 Still Failing - zopetoolkit_trunk - Build # 177 https://mail.zope.org/pipermail/zope-tests/2013-February/072575.html [2] FAILED Still Failing - zopetoolkit_trunk_app - Build # 159 https://mail.zope.org/pipermail/zope-tests/2013-February/072574.html [3] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072573.html [4] FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072571.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072597.html [6] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072558.html [7] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072556.html [8] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072569.html [9] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072598.html [10] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072559.html [11] FAILED winbot / z3c.password_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072564.html [12] FAILED winbot / z3c.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072560.html [13] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072596.html [14] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072570.html [15] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072566.html [16] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072562.html [17] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072557.html [18] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072565.html [19] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072572.html [20] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072561.html [21] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072563.html [22] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072568.html [23] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072567.html
TL;DR: three outstanding test failures where rendered HTML doesn't match expectations: - z3c.contents - z3c.layer.ready2go - z3c.tabular On Tue, Feb 19, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 177 https://mail.zope.org/pipermail/zope-tests/2013-February/072575.html
Build # 178: IOError: [Errno 2] No such file or directory: '/home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/src/zope.annotation/setup.py' zope.annotation was moved to Github very recently.
[4] FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072571.html
Success in next build!
[5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072597.html
Failure in next build: File "c:\buildslave\z3c.contents\build\src\z3c\contents\README.txt", line 111, in README.txt Failed example: print firstPage.render() Expected: (bunch of HTML) Got: (bunch of HTML) What an unhelpful test failure output. And +REPORT_NDIFF would not help, because the HTML is formatted rather differently. Some output normalization is sorely needed here.
[6] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072558.html
Success in next build!
[7] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072556.html
Success in next build!
[8] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072569.html
Success in next build!
[9] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072598.html
Failure in next build: File "c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\README.txt", line 384, in README.txt Failed example: print addForm.render() Expected: (bunch of HTML) Got: (bunch of HTML)
[10] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072559.html
Success in next build!
[11] FAILED winbot / z3c.password_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072564.html
Success in next build!
[12] FAILED winbot / z3c.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072560.html
Success in next build!
[13] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072596.html
Failure in next build: File "c:\buildslave\z3c.tabular\build\src\z3c\tabular\README.txt", line 124, in README.txt Failed example: print contentSubFormTable.render() Expected: (bunch of HTML) Got: (bunch of HTML)
[14] FAILED winbot / zc.sourcefactory_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072570.html
Success in next build!
[15] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072566.html
Success in next build!
[16] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072562.html
Success in next build!
[17] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072557.html
Success in next build!
[18] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072565.html
Success in next build!
[19] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072572.html
Success in next build!
[20] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072561.html
Success in next build!
[21] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072563.html
Success in next build!
[22] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072568.html
Success in next build!
[23] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072567.html
I pushed my workaround (with duplicate code extracted into a helper called _fmt_address) just now. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer