2013/4/26 Zope tests summarizer :
> This is the summary for test reports received on the
> zope-tests list between 2013-04-24 00:00:00 UTC and 2013-04-25 00:00:00 UTC:
>
> [1]FAILED Still Failing - zopetoolkit_trunk - Build # 244
>https://mail.zope.org/pipermail/zope-tests/2013-April/0
This is the summary for test reports received on the
zope-tests list between 2013-04-24 00:00:00 UTC and 2013-04-25 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/
2013/4/25 Marius Gedminas :
> On Thu, Apr 25, 2013 at 09:49:28AM -0400, Tres Seaver wrote:
>> On 04/25/2013 04:36 AM, Marius Gedminas wrote:
>> > So latest stable ZODB3 (3.10.5) is incompatible with the two latest
>> > stable persistent releases (4.0.5 and 4.0.6).
>> >
>> > What should we do? Rele
On Thu, Apr 25, 2013 at 09:49:28AM -0400, Tres Seaver wrote:
> On 04/25/2013 04:36 AM, Marius Gedminas wrote:
> > So latest stable ZODB3 (3.10.5) is incompatible with the two latest
> > stable persistent releases (4.0.5 and 4.0.6).
> >
> > What should we do? Release ZODB3 3.10.6 with a backport o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/25/2013 04:36 AM, Marius Gedminas wrote:
> On Thu, Apr 25, 2013 at 11:21:37AM +0300, Marius Gedminas wrote:
>> On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer
>> wrote:
>>> [3]winbot / z3c.contents_py_265_32
>>
>> Same old --
On Thu, Apr 25, 2013 at 11:21:37AM +0300, Marius Gedminas wrote:
> On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote:
> > [3]winbot / z3c.contents_py_265_32
>
> Same old -- and I just managed to reproduce it at last.
ZODB.utils.newTid(None) returns "'\\x03\\x9e8\\x9a:>\\x1
On Thu, Apr 25, 2013 at 01:00:01AM +, Zope tests summarizer wrote:
> [1]Still Failing - zopetoolkit_trunk - Build # 243
> [2]Still Failing - zopetoolkit_trunk - Build # 247
Same old
> [3]winbot / z3c.contents_py_265_32
Same old -- and I just managed to reproduce it at last.
> [4
