zope-tests - FAILED: 8, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-05-10 00:00:00 UTC and 2013-05-11 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 # 264 [2] winbot / ZEO_py_265_32 [3] winbot / ZODB_dev py_265_win32 [4] winbot / ZODB_dev py_265_win64 [5] winbot / ZODB_dev py_270_win32 [6] winbot / ZODB_dev py_270_win64 [7] winbot / zope.app.content_py_265_32 [8] winbot / zope.interface_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 # 264 https://mail.zope.org/pipermail/zope-tests/2013-May/074326.html [2] FAILED winbot / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074325.html [3] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074335.html [4] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074336.html [5] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074337.html [6] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074338.html [7] FAILED winbot / zope.app.content_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074339.html [8] FAILED winbot / zope.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074340.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/11/2013 09:00 PM, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 264 https://mail.zope.org/pipermail/zope-tests/2013-May/074326.html
I fixed an unpinned version for a new downstream dependency today. I think that will get us back to failing due to persistent / BTrees mismatches. :(
[2] FAILED winbot / ZEO_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074325.html
These tests are so slow and hard to work with that I lose patience with them. It looks like the ZEO tests are re-using some ZODB doctests, but without benefit of the renormalizers / checkers ZODB uses. I will look at exposing those items in ZODB, and have the ZEO tests reuse them.
[3] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074335.html
[4] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074336.html
[5] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-May/074337.html
[6] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-May/074338.html
I whacked another couple of Windows-only moles this weekend ('ZODB.utils.u64' returning a 'long', some file-not-closed bugs I introduced while trying to remove 'tempfile.mktemp'). I think I need keys to the winbot, or at least the ability to kick off a test run proactively.
[7] FAILED winbot / zope.app.content_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074339.html
[8] FAILED winbot / zope.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/074340.html
Github was offline. 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/ iEYEARECAAYFAlGO8LkACgkQ+gerLs4ltQ70RQCfap+HV93JBbFNNGy3M44NFZws PXoAoNNTSrd+KhMzSo+p61Wnw7ozkrC1 =Oc7Q -----END PGP SIGNATURE-----
participants (2)
-
Tres Seaver -
Zope tests summarizer