On Fri, Mar 15, 2013 at 01:00:01AM +, Zope tests summarizer wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 202
Back to regular failures:
- test-ztk-zope.traversing
- test-ztk-zope.dublincore
- test-ztk-zope.container
- test-ztk-zope.catalog
ImportError: No module named persistent
On Mar 15, 2013, at 07:57, Marius Gedminas mar...@gedmin.as wrote:
[8]winbot / zope.app.wsgi_py_265_32
I misunderstood last time. *** empty log message *** does not mean
this is a clone of an empty repo. It's *the actual svn commit message*
of the last commit:
On Fri, Mar 15, 2013 at 09:39:16AM +0100, Wichert Akkerman wrote:
On Mar 15, 2013, at 07:57, Marius Gedminas mar...@gedmin.as wrote:
[8]winbot / zope.app.wsgi_py_265_32
I misunderstood last time. *** empty log message *** does not mean
this is a clone of an empty repo. It's *the
This is the summary for test reports received on the
zope-tests list between 2013-03-13 00:00:00 UTC and 2013-03-14 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:
On Tue, Mar 12, 2013 at 01:00:02AM +, Zope tests summarizer wrote:
[1]Still Failing - zopetoolkit_trunk - Build # 199
Error: Picked: zope.security = 4.0.0b1
[2]winbot / z3c.contents_py_265_32
[3]winbot / z3c.form_py_265_32
[4]winbot / z3c.formui_py_265_32
[5]winbot /
This is the summary for test reports received on the
zope-tests list between 2013-03-10 00:00:00 UTC and 2013-03-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:
