On Tue, May 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[1]FAILED winbot / z3c.layer.ready2go_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/075191.html
Looks like a transient network glitch:
Reading http://pypi.python.org/simple/zope.interface/
On May 28, 2013, at 08:19, Marius Gedminas mar...@gedmin.as wrote:
On Tue, May 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[1]FAILED winbot / z3c.layer.ready2go_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-May/075191.html
Looks like a transient
This is the summary for test reports received on the
zope-tests list between 2013-05-27 00:00:00 UTC and 2013-05-28 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:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/28/2013 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Failure - zopetoolkit_trunk - Build # 278
https://mail.zope.org/pipermail/zope-tests/2013-May/075192.html
[2]FAILED Still Failing - zopetoolkit_trunk - Build # 279
On Tue, May 28, 2013 at 10:24:50PM -0400, Tres Seaver wrote:
On 05/28/2013 09:00 PM, Zope tests summarizer wrote:
[1]FAILED Failure - zopetoolkit_trunk - Build # 278
https://mail.zope.org/pipermail/zope-tests/2013-May/075192.html
[2]FAILED Still Failing - zopetoolkit_trunk