This is the summary for test reports received on the zope-tests list between 2014-01-07 00:00:00 UTC and 2014-01-08 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 ---------------- Fixed - zopetoolkit_trunk - Build # 508 [1] winbot / ZODB_dev py_265_win32 [2] winbot / ZODB_dev py_265_win64 [3] winbot / ZODB_dev py_270_win32 [4] winbot / ZODB_dev py_270_win64 [5] winbot / zope.app.container_py_265_32 [6] winbot / zope.app.i18n_py_265_32 [7] winbot / zope.hookable_py_265_32 [8] winbot / zope.i18nmessageid_py_265_32 [9] winbot / zope.proxy_py_265_32 [10] 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 winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080395.html [2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080396.html [3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080397.html [4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080398.html [5] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080399.html [6] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080400.html [7] FAILED winbot / zope.hookable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080402.html [8] FAILED winbot / zope.i18nmessageid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080403.html [9] FAILED winbot / zope.proxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080401.html [10] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080385.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080395.html
[2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080396.html
[3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080397.html
[4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080398.html
[5] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080399.html
[6] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080400.html
[7] FAILED winbot / zope.hookable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080402.html
[8] FAILED winbot / zope.i18nmessageid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080403.html
[9] FAILED winbot / zope.proxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080401.html
These are all failures in the 'git' phase (presumably transient network / github outages).
[10] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080385.html
This is the hex address case-sensitivity bug, which Marius whack-a-moled today: https://github.com/zopefoundation/zope.security/commit/45e8a8563dcbc82c615fb... Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLN78kACgkQ+gerLs4ltQ6DqwCfaCjFbk5ERGTnn1+eIsx3PWov dO0An3BybRVBy15Oo8dfh8mhCACOr+RM =qpWm -----END PGP SIGNATURE-----
On Wed, Jan 08, 2014 at 07:39:41PM -0500, Tres Seaver wrote:
On 01/08/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080395.html
[2] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080396.html
[3] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2014-January/080397.html
[4] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2014-January/080398.html
[5] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080399.html
[6] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080400.html
[7] FAILED winbot / zope.hookable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080402.html
[8] FAILED winbot / zope.i18nmessageid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080403.html
[9] FAILED winbot / zope.proxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080401.html
These are all failures in the 'git' phase (presumably transient network / github outages).
[10] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-January/080385.html
This is the hex address case-sensitivity bug, which Marius whack-a-moled today:
https://github.com/zopefoundation/zope.security/commit/45e8a8563dcbc82c615fb...
Only there were two moles, and I fixed but one in that commit, *sigh* https://github.com/zopefoundation/zope.security/commit/01f798705f7dae5fcc822... should fix them both. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Marius Gedminas -
Tres Seaver -
Zope tests summarizer