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