This is the summary for test reports received on the zope-tests list between 2013-08-11 00:00:00 UTC and 2013-08-12 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 # 357 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/2013-August/078256.html
On Tue, Aug 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote:
[1] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-August/078256.html
Nondeterministic timeout: File "c:\buildslave\zc.ngi\build\src\zc\ngi\doc\index.txt", line 185, in index.txt Failed example: zc.ngi.async.connect(listener.address, one); zc.ngi.async.wait(1) Exception raised: Traceback (most recent call last): File "c:\Python26_32\lib\doctest.py", line 1253, in __run compileflags, 1) in test.globs File "<doctest index.txt[0]>", line 1, in <module> zc.ngi.async.connect(listener.address, one); zc.ngi.async.wait(1) File "c:\buildslave\zc.ngi\build\src\zc\ngi\async.py", line 118, in wait raise zc.ngi.interfaces.Timeout Timeout Last build succeeded despite running the exact same version of the zc.ngi code. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer