This is the summary for test reports received on the
zope-tests list between 2012-07-19 00:00:00 UTC and 2012-07-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/
On Mon, Jul 09, 2012 at 10:24:29PM -0400, Tres Seaver wrote:
> On 07/09/2012 09:00 PM, Zope tests summarizer wrote:
> > [1]FAILED Zope 3.4 Known Good Set / py2.5-32bit-linux
> > https://mail.zope.org/pipermail/zope-tests/2012-July/065159.html
>
> Blew chunks while creating its virtualenv san
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/2012 09:00 PM, Zope tests summarizer wrote:
> [1]FAILED Zope 3.4 Known Good Set / py2.5-32bit-linux
> https://mail.zope.org/pipermail/zope-tests/2012-July/065159.html
Blew chunks while creating its virtualenv sandbox (transient network
This is the summary for test reports received on the
zope-tests list between 2012-07-08 00:00:00 UTC and 2012-07-09 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, Jul 7, 2012 at 4:45 PM, Tres Seaver wrote:
> BTW, can somebody tell me again why we are running nightly tests against
> the released versions of ZTK 1.0?
And ZTK 1.1 and KGS 3.4:
http://buildbot.afpy.org/ztk1.0/
http://buildbot.afpy.org/ztk1.1/
http://buildbot.afpy.org/kgs3.4/
--
Seb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/06/2012 09:00 PM, Zope tests summarizer wrote:
> [1]FAILED winbot / ztk_10 py_254_win32
> https://mail.zope.org/pipermail/zope-tests/2012-July/065094.html
Undiagnosable:
race condition + doctest + unmaintained zope.testing.testrunner
I
This is the summary for test reports received on the
zope-tests list between 2012-07-05 00:00:00 UTC and 2012-07-06 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/