This is the summary for test reports received on the zope-tests list between 2014-04-12 00:00:00 UTC and 2014-04-13 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 ---------------- Successful - zopetoolkit_trunk - Build # 604 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1] winbot / zc.ngi_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 / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-April/081748.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/13/2014 07:00 PM, Zope tests summarizer wrote:
[1] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2014-April/081748.html
I can't reproduce the doctest failure: 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 The code hasn't changed in two years. The line *after* the failing line is:
time.sleep(0.5)
Smells like day-old fish to me. 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/ iEYEARECAAYFAlNLU5oACgkQ+gerLs4ltQ43bgCfRTc2Qp2j/YdaAwBFc5N8EiNn MVcAnjZOF3Z9szr1LDyorXzPfmhbhPC9 =78Pj -----END PGP SIGNATURE-----
participants (2)
-
Tres Seaver -
Zope tests summarizer