Op 11/01/16 om 01:00 schreef Zope tests summarizer:

This is the summary for test reports received on the zope-tests list between 2016-01-09 00:00:00 UTC and 2016-01-10 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] Failure - zopetoolkit_trunk - Build # 1234 [2] winbot / zc.ngi_py_265_32 [3] winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 [4] winbot / ztk_11 py_254_win32 [5] winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64

Non-OK results --------------

[1] FAILED Failure - zopetoolkit_trunk - Build # 1234 https://mail.zope.org/pipermail/zope-tests/2016-January/092082.html

Connection timed out connecting with PyPI.

[2] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2016-January/092081.html

File "c:\buildslave\zc.ngi\build\src\zc\ngi\tests.py", line 541, in zc.ngi.tests.EXPERIMENTAL_thready_async_servers Failed example: listener.close() Expected nothing Got: -> CLOSE end of input No recent release or commits in zc.ngi, so maybe temporary failure?

[3] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2016-January/092083.html

Known failure. I think we still want to shut this one down.

[4] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2016-January/092086.html

Same.

[5] FAILED winbot / ztk_11 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2016-January/092087.html

Heh, a long diff for d:\eggs\zope.testrunner-4.0.4-py2.6.egg\zope\testrunner\testrunner-layers.txt", line 130, in testrunner-layers.txt, which boils down to this: Expected: Total: 321 tests, 0 failures, 0 errors in N.NNN seconds. Got: Total: 321 tests, 0 failures, 0 errors in 1 minutes N.NNN seconds. Theoretically we could probably fix this to accept the '1 minutes' extra, but that require changing the tests.py file on an old zope.testrunner branch and making a new release: https://github.com/zopefoundation/zope.testrunner/blob/4.0/src/zope/testrunn... Or we accept that this test occasionally breaks when the testrunner is slower than usual. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl