zope-tests - FAILED: 2, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-10-31 00:00:00 UTC and 2013-11-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 ---------------- Successful - zopetoolkit_trunk - Build # 445 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 / zope.mimetype_py_265_32 [2] 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 / zope.mimetype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079484.html [2] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-November/079486.html
On Sat, Nov 02, 2013 at 01:00:02AM +0100, Zope tests summarizer wrote:
[1] FAILED winbot / zope.mimetype_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-November/079484.html
Transient network failure during git pull.
[2] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-November/079486.html
zope.dublincore (3.7.0) has a bug that makes a test fail when the number of microseconds in a timestamp happens to be zero. Fixed in 3.8.2. If ZTK 1.0 is still supported, maybe we should backport that fix and release 3.7.1. If not, maybe we should turn off ZTK 1.0 buildbot runs. Who decides these things? Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
zope.dublincore (3.7.0) has a bug that makes a test fail when the number of microseconds in a timestamp happens to be zero.
Fixed in 3.8.2.
If ZTK 1.0 is still supported, maybe we should backport that fix and release 3.7.1.
- -0
If not, maybe we should turn off ZTK 1.0 buildbot runs.
+1
Who decides these things?
Qui facit, iudicat. 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/ iEYEARECAAYFAlJ3poUACgkQ+gerLs4ltQ6qcACeL0PJN6wmXkCy++DkyWGZGNDd drwAoKFqWD/AwgzZpwQNpJWv+5hLITHf =qdE8 -----END PGP SIGNATURE-----
On Mon, Nov 04, 2013 at 08:52:11AM -0500, Tres Seaver wrote:
zope.dublincore (3.7.0) has a bug that makes a test fail when the number of microseconds in a timestamp happens to be zero.
Fixed in 3.8.2.
If ZTK 1.0 is still supported, maybe we should backport that fix and release 3.7.1.
-0
If not, maybe we should turn off ZTK 1.0 buildbot runs.
+1
Who decides these things?
Qui facit, iudicat.
If http://docs.zope.org/zopetoolkit/process/buildbots.html#linux can be trusted, it's up to AFPY then. Incidentally, I shut down the even older ZTK 3.4 KGS buildbot a while ago, and, to my shame, didn't update this page (because I don't remember where the source of that buildbots.html lives. I demand an "Edit on GitHub" link right on the page for us memory-impaired ... uh, what am I talking about?) Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Marius Gedminas -
Tres Seaver -
Zope tests summarizer