On Thu, Feb 21, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
This is the summary for test reports received on the zope-tests list between 2013-02-19 00:00:00 UTC and 2013-02-20 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] FAILED (failures=2) : Zope-2.13 Python-2.6.8 : Linux [2] FAILED (failures=2) : Zope-2.13 Python-2.7.3 : Linux [3] FAILED (failures=2) : Zope-trunk Python-2.6.8 : Linux [4] FAILED (failures=2) : Zope-trunk Python-2.7.3 : Linux
Same old. (These emails have no link to the buildbot build, so I can't peek at future results.)
[5] Still Failing - zopetoolkit_trunk - Build # 179 [6] Still Failing - zopetoolkit_trunk_app - Build # 161
Same old. (I haven't tried to add new ZODB to the ZTK yet. Maybe someone else will get to it first, hint, hint ;)
[7] winbot / z3c.contents_py_265_32 [8] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.tabular_py_265_32
Same old. (Can't reproduce locally.)
[9] winbot / z3c.recipe.paster_py_265_32
This is new: Error: Couldn't find a distribution for 'zope.browserpage'. inside the test, i.e. in that fake zc.buildout.testing environment. Interesting.
[11] winbot / zope.copy_py_265_32 [12] winbot / zope.exceptions_py_265_32 [13] winbot / zope.hookable_py_265_32 [14] winbot / zope.i18n_py_265_32 [15] winbot / zope.lifecycleevent_py_265_32 [16] winbot / zope.location_py_265_32 [17] winbot / zope.proxy_py_265_32 [18] winbot / zope.testing_py_265_32
These are all green in their latest builds.
[19] winbot / zope.traversing_py_265_32
Moved to github, winbot lags as usual. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development