On May 28, 2013, at 08:19, Marius Gedminas 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 network glitch:
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/
This is the summary for test reports received on the
zope-tests list between 2013-05-26 00:00:00 UTC and 2013-05-27 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/
On Sat, May 25, 2013 at 01:00:01AM +, 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
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/
