On Wed, Feb 20, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:

This is the summary for test reports received on the zope-tests list between 2013-02-18 00:00:00 UTC and 2013-02-19 00:00:00 UTC:

I finally got tired of clicking at the links by hand and wrote a script: https://gist.github.com/mgedmin/4995950 It gives me output like this: http://zope3.pov.lt/zope-tests-2013-02-20.html

[1] UNKNOWN FAILED (failures=2) : Zope-2.13 Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072605.html

Failure in test test_menu (Products.Five.browser.tests.test_menu) Failed example: pprint(menu[1]) Expected: {'action': u'@@cockatiel_menu_public.html', ... Got: {'action': '@@cockatiel_menu_public.html', ... Failure in test /home/stefan/autotest/temp/python26-zope213all/src/Products/Five/browser/tests/pages.txt Failed example: page.__name__ Expected: u'eagle.txt' Got: 'eagle.txt'

[2] UNKNOWN FAILED (failures=2) : Zope-2.13 Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072606.html

Same two failures.

[3] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072607.html

Same two failures.

[4] UNKNOWN FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072608.html

Same two failures.

[5] FAILED Still Failing - zopetoolkit_trunk - Build # 178 https://mail.zope.org/pipermail/zope-tests/2013-February/072600.html

Error: Picked: BTrees = 4.0.5 So now zope.annotation requires BTrees, which is not part of the ZTK. Two options: * pin zope.annotation to an older branch that didn't require BTrees * add BTrees and the other exploded-ZODB3-packages to the ZTK, switch ZODB3 from the 3.10 branch to trunk

[6] FAILED Still Failing - zopetoolkit_trunk_app - Build # 160 https://mail.zope.org/pipermail/zope-tests/2013-February/072601.html

Same.

[7] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072623.html

Same incomprehensible HTML diff. Adam ran it by hand with --ndiff on winbot and reported that the difference is a different ordering of id and menu attributes on the outer <form> element: Expected: <form ... name="contents" id="contents"> Actual: <form ... id="contents" name="contents"> I'd like to know why I can't reproduce this locally. This could be caused by changes in zope.tal 4.0.0a1: it outputs dynamic attributes in alphabetical order (instead of dictionary iteration order), but this should cause the same failure on all platforms, not just Windows.

[8] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072628.html

Same.

[9] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072622.html

Same.

[10] FAILED winbot / zope.deprecation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072621.html

Moved to github, zope.wineggbuilder needs an update.

[11] FAILED winbot / zope.event_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072627.html

Moved to github, zope.wineggbuilder needs an update.

[12] FAILED winbot / zope.i18nmessageid_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072624.html

Moved to github, zope.wineggbuilder needs an update.

[13] FAILED winbot / zope.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072626.html

Moved to github, zope.wineggbuilder needs an update.

[14] FAILED winbot / zope.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072625.html

Moved to github, zope.wineggbuilder needs an update.

[15] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072599.html

Latest build is all green. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development