zope-tests - FAILED: 9, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-05-18 00:00:00 UTC and 2013-05-19 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- [1] Still Failing - zopetoolkit_trunk - Build # 269 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.datagenerator_py_265_32 [3] winbot / zope.app.locales_py_265_32 [4] winbot / zope.componentvocabulary_py_265_32 [5] winbot / zope.keyreference_py_265_32 [6] winbot / zope.password_py_265_32 [7] winbot / zope.publisher_py_265_32 [8] winbot / zope.security_py_265_32 [9] winbot / zope.tal_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 269 https://mail.zope.org/pipermail/zope-tests/2013-May/075067.html [2] FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075062.html [3] FAILED winbot / zope.app.locales_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075066.html [4] FAILED winbot / zope.componentvocabulary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075060.html [5] FAILED winbot / zope.keyreference_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075065.html [6] FAILED winbot / zope.password_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075061.html [7] FAILED winbot / zope.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075064.html [8] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075059.html [9] FAILED winbot / zope.tal_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-May/075063.html
On Mon, May 20, 2013 at 01:00:01AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 269
Same old issue with sys.path lacking persistent.
[2] winbot / z3c.datagenerator_py_265_32 [3] winbot / zope.app.locales_py_265_32 [4] winbot / zope.componentvocabulary_py_265_32 [5] winbot / zope.keyreference_py_265_32 [6] winbot / zope.password_py_265_32 [7] winbot / zope.publisher_py_265_32 [8] winbot / zope.security_py_265_32 [9] winbot / zope.tal_py_265_32
Last builds succeeded for all of these. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/20/2013 01:57 AM, Marius Gedminas wrote:
On Mon, May 20, 2013 at 01:00:01AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 269 Same old issue with sys.path lacking persistent.
I "fixed" this by removing the checkouts of the non-ZTK packages from the buildout. I made this change after spending an hour this morning trying to isolate the differences between the way the working set was computed in the ZTK buildout vs. one of the failing packages (zope.traversing). In the end, I couldn't figure out why the presence of the '.egg-links' for persistent / BTrees / ZODB / ZODB3 / ZEO in the 'develop-eggs' directory was causing the breakgage, but I also lost my will to care. 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.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlGaNk8ACgkQ+gerLs4ltQ4o+QCgj5gbqOSVo5mxV5spX39dnfu+ WzEAoM96PBxU0EMxAS6XewF5DpCm1Alw =U369 -----END PGP SIGNATURE-----
participants (3)
-
Marius Gedminas -
Tres Seaver -
Zope tests summarizer