[Zope-dev] zope-tests - FAILED: 2, OK: 17, UNKNOWN: 3

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/14/2012 09:10 PM, Tres Seaver 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.

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.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at 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/

iEYEARECAAYFAlDM0wAACgkQ+gerLs4ltQ70qQCgrJyvaW5gsjSKhieNQodrFObm
GZ0AnjoGlfjkBHplw9NLgIo3WTnQCngS
=YS6U
-----END PGP SIGNATURE-----