-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit > From: ccomb at free.fr > Date: Thu Mar 3 22:13:09 EST 2011 > URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033836.html > > Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit > From: ccomb at free.fr > Date: Thu Mar 3 22:13:26 EST 2011 > URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033837.html > > Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit > From: ccomb at free.fr > Date: Thu Mar 3 22:13:40 EST 2011 > URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033838.html This is some infuruating doctest-based failure in /home/ccomb/ztk1.0dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testing/src/zope/testing/testrunner/testrunner-layers-buff.txt I'm never gonna diagnose that one. In re the various 'z3c' failures: if we can't pin them to an earlier lxml version, can we at least disable them until we have the lxml binary available? The noise is counterproductive. 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.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1xCfcACgkQ+gerLs4ltQ7sWwCfTBklPQ4pEX7S4FV0qQUD+qC8 ossAn3mLDIF4nMoKRNsfKFtgwFgUjI6g =qw+J -----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 )