This is the summary for test reports received on the zope-tests list between 2013-02-12 00:00:00 UTC and 2013-02-13 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 # 171 [2] Still Failing - zopetoolkit_trunk_app - Build # 154 [3] Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux [4] winbot / ZODB_dev py_265_win32 [5] winbot / ZODB_dev py_265_win64 [6] winbot / ZODB_dev py_270_win32 [7] winbot / ZODB_dev py_270_win64 [8] winbot / z3c.datagenerator_py_265_32 [9] winbot / z3c.recipe.paster_py_265_32 [10] winbot / zc.ngi_py_265_32 [11] winbot / zope.container_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 # 171 https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html [2] FAILED Still Failing - zopetoolkit_trunk_app - Build # 154 https://mail.zope.org/pipermail/zope-tests/2013-February/072266.html [3] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072268.html [4] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072285.html [5] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072286.html [6] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072287.html [7] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072288.html [8] FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072292.html [9] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072289.html [10] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072290.html [11] FAILED winbot / zope.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072291.html
On Thu, Feb 14, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 171 https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html
Same zope.container error as yesterday. There's a Build # 172 as well, which fails curiously, while in buildout: While: Installing test-ztk. Getting distribution for 'zope.container'. Error: Picked: zope.container = 3.12.0 This error message never made sense to me. Maybe the buildout config (which I can't quickly check since it's password-protected in that Jenkins instance, annoying) has allow-picked-versions=false? I'm stumped.
[2] FAILED Still Failing - zopetoolkit_trunk_app - Build # 154 https://mail.zope.org/pipermail/zope-tests/2013-February/072266.html
Same as above.
[3] FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072268.html
zope.testing 3.5.6 with a broken testrunner-coverage.txt (Apparently this test has been broken for a long time, but email notifications were broken due to a buildbot upgrade.) I'm tempted to investigate, but does anybody use the ancient 3.4 KGS any more? Perhaps I ought to shut this buildbot down. (Or repurpose it to test something more modern.)
[4] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072285.html
Broken manuel 1.7.0 release on PyPI (missing CHANGES.txt), already fixed in 1.7.1
[5] FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072286.html
[6] FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072287.html
[7] FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072288.html
Didn't check, assume same as above.
[8] FAILED winbot / z3c.datagenerator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072292.html
winbot not restarted to pick up source repository change.
[9] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072289.html
Oh, look, it's not the old weird error nobody fixed yet. It's a new and popular error about AttributeError: 'NoneType' object has no attribute 'location' in the bowels of zc.buildout-2.0.0-py2.6.egg. z3c.recipe.paster needs an updated bootstrap.py Will update and see what happens.
[10] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072290.html
manuel 1.7.0 broke this one too.
[11] FAILED winbot / zope.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072291.html
winbot not restarted to pick up source repository change. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas <marius@gedmin.as> wrote:
On Thu, Feb 14, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 171
https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html
Same zope.container error as yesterday.
There's a Build # 172 as well, which fails curiously, while in buildout:
While: Installing test-ztk. Getting distribution for 'zope.container'. Error: Picked: zope.container = 3.12.0
This error message never made sense to me.
Maybe the buildout config (which I can't quickly check since it's password-protected in that Jenkins instance, annoying) has allow-picked-versions=false?
I use the regular development.cfg. I just delete some test file, that's all about the specifics. development.cfg extends buildout, which in turn has this setting set. I am stumped too for now. All settings seem to be correct. Also, for completeness sake, my jenkins always starts a totally fresh buildout, there is no residue left behind. In other news, I added two more builders, they do not run every night, but with every commit to ztk. They are not as clean as the nightlies, they only delete the source directory before the builds. They also do not send mails to the mailing list. I'll add anybody who wants it to the notification list. Additionally, I'll create accounts for everybody who wants to help with tests on request. Tres and Marius got one already. Best regards, Patrick
Hah, that zope.container problem wasn't all that hard after all. http://svn.zope.org/zopetoolkit/trunk/ztk-sources.cfg?rev=129373&view=diff&r... On Thu, Feb 14, 2013 at 10:38 AM, Patrick Gerken <do3ccqrv@googlemail.com>wrote:
On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas <marius@gedmin.as> wrote:
On Thu, Feb 14, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] FAILED Still Failing - zopetoolkit_trunk - Build # 171
https://mail.zope.org/pipermail/zope-tests/2013-February/072267.html
Same zope.container error as yesterday.
There's a Build # 172 as well, which fails curiously, while in buildout:
While: Installing test-ztk. Getting distribution for 'zope.container'. Error: Picked: zope.container = 3.12.0
This error message never made sense to me.
Maybe the buildout config (which I can't quickly check since it's password-protected in that Jenkins instance, annoying) has allow-picked-versions=false?
I use the regular development.cfg. I just delete some test file, that's all about the specifics.
development.cfg extends buildout, which in turn has this setting set.
I am stumped too for now. All settings seem to be correct. Also, for completeness sake, my jenkins always starts a totally fresh buildout, there is no residue left behind.
In other news, I added two more builders, they do not run every night, but with every commit to ztk. They are not as clean as the nightlies, they only delete the source directory before the builds. They also do not send mails to the mailing list. I'll add anybody who wants it to the notification list. Additionally, I'll create accounts for everybody who wants to help with tests on request. Tres and Marius got one already.
Best regards,
Patrick
On Thu, Feb 14, 2013 at 10:46:35AM +0100, Patrick Gerken wrote:
Hah,
that zope.container problem wasn't all that hard after all.
http://svn.zope.org/zopetoolkit/trunk/ztk-sources.cfg?rev=129373&view=diff&r...
Haha. My fault. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (3)
-
Marius Gedminas -
Patrick Gerken -
Zope tests summarizer