-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/18/2012 09:00 PM, Zope tests summarizer wrote:
[1] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2012-April/060745.html
[2] UNKNOWN UNKNOWN : winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2012-April/060746.html
These are timeouts during the 'test-zopeapp' phase. I can't diagnose anything more from the buildbot output.
[3] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060730.html
[4] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060729.html
[5] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060728.html
[6] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060725.html
[7] FAILED ZTK 1.1dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060726.html
[8] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2012-April/060727.html
These are all failures due to an (inappropriate) pull of some trunk package which now depends on repoze.sphinx.autointerface. I'm planning to create "stable" branches for all the packages I have touched lately which might be causing this, and pin the ZTK 1.0dev and 1.1dev buildouts to use them. FWIW, I'm now more convinced than ever that we shouldn't be using trunk checkouts for *any* packages in those builds, but I won't argue for that again. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@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/ iEYEARECAAYFAk+QUnQACgkQ+gerLs4ltQ6C+QCcDPXUszh7MYHp4kX6+I/4B6y5 dc4AoIxcrg2OJNTjX0QCR+TgtJxnetlt =8ln4 -----END PGP SIGNATURE-----