On Fri, May 24, 2013 at 09:31:55PM -0400, Tres Seaver wrote:
On 05/24/2013 01:28 PM, Marius Gedminas wrote:
I was trying to debug a failing ZEO test case
(testConcurrentUpdates), and found out it had nothing to do with
ZEO. There's a bug either in BTrees or in ZODB itself that causes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2013 02:50 AM, Marius Gedminas wrote:
On Fri, May 24, 2013 at 09:31:55PM -0400, Tres Seaver wrote:
On 05/24/2013 01:28 PM, Marius Gedminas wrote:
I was trying to debug a failing ZEO test case
(testConcurrentUpdates), and found out it had
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2013 11:49 AM, Tres Seaver wrote:
On 05/25/2013 02:50 AM, Marius Gedminas wrote:
On Fri, May 24, 2013 at 09:31:55PM -0400, Tres Seaver wrote:
On 05/24/2013 01:28 PM, Marius Gedminas wrote:
I was trying to debug a failing ZEO test case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2013 01:36 PM, Tres Seaver wrote:
I am trying to reproduce the ZEO test failure now, and then against
the BTrees trunk, before making a BTrees release.
Rather than relying on the slow and somewhat non-deterministic ZEO
failures, I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2013 01:43 PM, Tres Seaver wrote:
I will make a BTrees 4.0.7 release shortly.
That would be 4.0.8:
https://pypi.python.org/pypi/BTrees/4.0.8
Tres.
- --
===
Tres Seaver
I was trying to debug a failing ZEO test case (testConcurrentUpdates),
and found out it had nothing to do with ZEO. There's a bug either in
BTrees or in ZODB itself that causes data corruption under Python 3.x.
Here's a test case:
https://gist.github.com/mgedmin/5644876#file-zodbfail_simple-py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/24/2013 01:28 PM, Marius Gedminas wrote:
I was trying to debug a failing ZEO test case
(testConcurrentUpdates), and found out it had nothing to do with ZEO.
There's a bug either in BTrees or in ZODB itself that causes data
corruption under
