-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/14/2012 08:00 PM, Zope tests summarizer wrote: > [1] UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win32 > https://mail.zope.org/pipermail/zope-tests/2012-December/070119.html > > > [2] UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win64 > https://mail.zope.org/pipermail/zope-tests/2012-December/070120.html > > > [3] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 > https://mail.zope.org/pipermail/zope-tests/2012-December/070121.html
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. > [4] FAILED winbot / z3c.ptcompat_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-December/070100.html Dunno about this one. > [5] FAILED winbot / z3c.recipe.paster_py_265_32 > https://mail.zope.org/pipermail/zope-tests/2012-December/070101.html This one is failing to install a BTrees release. I'm not sure why: maybe related to the hang on the builder? Tres. - -- =================================================================== 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/ iEYEARECAAYFAlDL3BAACgkQ+gerLs4ltQ55uQCgvVRNlJP0q0bBxtiJFpQPlba7 OV0AoNnxPhL6BKIXjoNQt/mm7Sh/9B8n =nAFI -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )