This is the summary for test reports received on the zope-tests list between 2013-03-31 00:00:00 UTC and 2013-04-01 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] Still Failing - zopetoolkit_trunk - Build # 220 [2] winbot / ZODB_dev py_265_win32 [3] winbot / ZODB_dev py_265_win64 [4] winbot / ZODB_dev py_270_win32 [5] winbot / z3c.contents_py_265_32 [6] winbot / z3c.form_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 Still Failing - zopetoolkit_trunk - Build # 220 https://mail.zope.org/pipermail/zope-tests/2013-April/073643.html [2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073653.html [3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073654.html [4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073655.html [5] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073644.html [6] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-April/073642.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/01/2013 09:00 PM, Zope tests summarizer wrote:
[2] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073653.html
[3] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-April/073654.html
[4] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-April/073655.html
These all look to be a borked renormalizer: - ---------------------------------------------------------------------- Expected: Traceback (most recent call last): ... POSKeyError: 'No blob file at <BLOB STORAGE PATH>' Got: Traceback (most recent call last): File "c:\Python26_32\lib\doctest.py", line 1253, in __run compileflags, 1) in test.globs File "<doctest blob_transaction.txt[150]>", line 1, in <module> blob_storage.loadBlob(blob._p_oid, s1) File "c:\buildslave\zodb_dev_py_265_win32\build\src\ZODB\blob.py", line 645, in loadBlob raise POSKeyError("No blob file at %s" % filename, oid, serial) POSKeyError: 'No blob file at c:\\buildslave\\ZODB_dev_py_265_win32\\build\\parts\\test\\tmp\\testwzejdj\\blobs\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x00\\0x05\\0x039db52c5b76ebab.blob' - ---------------------------------------------------------------------- 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 undefined - http://www.enigmail.net/ iEYEARECAAYFAlFa54YACgkQ+gerLs4ltQ5ragCgia5bO4cz2pIECPSM4x2ABeqo 8v8AoNbeyXGMpHipBQ22iA2qS3/XVze6 =OmZ3 -----END PGP SIGNATURE-----
participants (2)
-
Tres Seaver -
Zope tests summarizer