Hello,
I also suggest dropping the test reports for the z3c.* packages: they
have been broken since the day they were added, AFAICT, which is a
strong signal that they are not being maintained.
The point of the daily reports is to *keep the board green*, so that
when a new failure shows
Hello,
On Mon, 28 Feb 2011 14:08:29 -0500 you wrote:
On Monday, February 28, 2011, Tres Seaver wrote:
I also suggest dropping the test reports for the z3c.* packages: they
have been broken since the day they were added, AFAICT, which is a
strong signal that they are not being maintained.
On Tue, Mar 1, 2011 at 10:27 AM, Adam GROSZER agroszer...@gmail.com wrote:
Hello,
On Mon, 28 Feb 2011 14:08:29 -0500 you wrote:
On Monday, February 28, 2011, Tres Seaver wrote:
I also suggest dropping the test reports for the z3c.* packages: they
have been broken since the day they
Hello,
On Tue, 1 Mar 2011 11:04:30 +0100 you wrote:
The build of z3c.* packages on winbot could be tested like
http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161
build
On Tue, Mar 1, 2011 at 11:42 AM, Adam GROSZER agroszer...@gmail.com wrote:
Hello,
On Tue, 1 Mar 2011 11:04:30 +0100 you wrote:
The build of z3c.* packages on winbot could be tested like
http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161
build
Summary of messages to the zope-tests list.
Period Mon Feb 28 12:00:00 2011 UTC to Tue Mar 1 12:00:00 2011 UTC.
There were 97 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 27 from
buildbot at winbot.zope.org, 11 from ccomb at free.fr, 47 from jdriessen at
thehealthagency.com.
Test
Hello,
Subject: FAILED : winbot / z3c.form_py_265_32
From: buildbot at winbot.zope.org
Date: Mon Feb 28 22:25:47 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033471.html
Now it seems like Malthe is the one to blaim...
Good to have those bots, or not ;-)
--
Best
On 2011-02-28 07:43:55 +0100, Christian Zagrodnick said:
On 2011-02-25 21:56:49 +0100, David Glick said:
On 2/20/11 1:32 AM, Christian Zagrodnick wrote:
On 2011-02-19 17:17:44 +0100, Hanno Schlichting said:
On Thu, Feb 17, 2011 at 8:27 AM, Christian Zagrodnickc...@gocept.com
wrote:
On
On 3/1/11 11:57 AM, Christian Zagrodnick wrote:
This change introduces a regression when calling unicode on wrapped
objects that implement __str__ but not __unicode__. Essentially it is
now doing the equivalent of str(aq_base(obj)) ... __str__ used to get a
wrapped object as 'self', but now it
