-----BEGIN PGP SIGNED MESSAGE-----
On 12/14/2012 09:10 PM, Tres Seaver wrote:
>>>  UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win32
>>>  UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win64
>>>  UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32
These three are at least partly my fault: the new persistent release
> enforces that tids are bytes objects, but ZODB still computed them
> via 'repr(timestamp)', which is a string. I have checked in a change
> which make ZODB us 'timestamp.raw()' instead. There are still some
> failures to work through.
I have checked in changes which have the ZODB trunk tests passing now
under Python 2.6 2.7.
Looking at the tests list page: I see a bunch of failures related to the
same ZODB issues; those should clear up after tonights report.
There are some BTrees failures on Windows which are not related to the
persistent change: they look to be due to Windows long vs. longlong stuff.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -