This is the summary for test reports received on the zope-tests list between 2013-05-23 00:00:00 UTC and 2013-05-24 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 # 274 [1] winbot / ZEO_py_265_32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 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 / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075138.html
On Sat, May 25, 2013 at 01:00:01AM +0000, Zope tests summarizer wrote:
[1] winbot / ZEO_py_265_32
Build #67 with same old error Build #68 was successful (yay! my last fix worked!) Build #69 failed in Git with a WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\buildslave\\ZEO\\build' Probably because I left an rdesktop session with a shell open in that working directory. Aaaugh, Windows, grow up. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer