zope-tests - FAILED: 15, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-03-01 00:00:00 UTC and 2013-03-02 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 # 189 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.contents_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [5] winbot / z3c.language.switch_py_265_32 [6] winbot / z3c.layer.pagelet_py_265_32 [7] winbot / z3c.pagelet_py_265_32 [8] winbot / zc.resourcelibrary_py_265_32 [9] winbot / zope.app.authentication_py_265_32 [10] winbot / zope.app.http_py_265_32 [11] winbot / zope.app.pagetemplate_py_265_32 [12] winbot / zope.app.publication_py_265_32 [13] winbot / zope.app.renderer_py_265_32 [14] winbot / zope.browserpage_py_265_32 [15] winbot / zope.formlib_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 # 189 https://mail.zope.org/pipermail/zope-tests/2013-March/072982.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072979.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072975.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072978.html [5] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072981.html [6] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072996.html [7] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072974.html [8] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073000.html [9] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072998.html [10] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072999.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072976.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072997.html [13] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072980.html [14] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072995.html [15] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072977.html
On Sun, Mar 03, 2013 at 01:00:01AM +0000, Zope tests summarizer wrote:
[1] Still Failing - zopetoolkit_trunk - Build # 189
Error: Picked: zope.untrustedpython = 4.0.0 mr.developer: Can't switch package 'z3c.recipe.compattest' to '^/z3c.recipe.compattest/trunk' because it's dirty.
[2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [7] winbot / z3c.pagelet_py_265_32
No lxml
[5] winbot / z3c.language.switch_py_265_32
No zope.app.testing
[6] winbot / z3c.layer.pagelet_py_265_32
No webtest
[8] winbot / zc.resourcelibrary_py_265_32
WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-rz412g'
[9] winbot / zope.app.authentication_py_265_32
The unicode thing
[10] winbot / zope.app.http_py_265_32
No zope.testbrowser.wsgi
[11] winbot / zope.app.pagetemplate_py_265_32
\r\n
[12] winbot / zope.app.publication_py_265_32
No zope.testbrowser.wsgi
[13] winbot / zope.app.renderer_py_265_32
Initialized empty Git repository in c:/buildslave/zope.app.renderer/source/.git/ fatal: remote error: Repository not found. zope.app.renderer doesn't exist on github! But http://zope3.pov.lt/trac/browser/zope.app.renderer/trunk/MOVED_TO_GITHUB claims it does. My guess: some automated script is missing some error checking (e.g. for "github said repository was not created"). Stephan, do you still have a copy of that git repo on your laptop?
[14] winbot / zope.browserpage_py_265_32
\r\n
[15] winbot / zope.formlib_py_265_32
Moved to github; I fixed the wineggbuilder URL yesterday but I don't know the procedure for svnuping and restarting winbot. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
On Sunday, March 03, 2013 11:48:01 AM Marius Gedminas wrote:
[2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [7] winbot / z3c.pagelet_py_265_32
No lxml
Can we set up our windows box to build lxml binaries and upload them to PyPI? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"
On 03/03/2013 10:07 PM, Stephan Richter wrote:
On Sunday, March 03, 2013 11:48:01 AM Marius Gedminas wrote:
[2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [7] winbot / z3c.pagelet_py_265_32
No lxml
Can we set up our windows box to build lxml binaries and upload them to PyPI?
I'll try to bug the guy behind http://www.lfd.uci.edu/~gohlke/pythonlibs Seems like he has the recipe for it. Then we just need to convince Martijn to give the bot perm on pypi. -- Best regards, Adam GROSZER -- Quote of the day: Infidelity is seated in the heart; its origin is not in the head. It is the wish that Christianity might not be true, that leads to an argument to prove it. - Charles Simmons
On Sun, Mar 3, 2013 at 2:00 AM, Zope tests summarizer <noreply@zope.org>wrote:
This is the summary for test reports received on the zope-tests list between 2013-03-01 00:00:00 UTC and 2013-03-02 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 # 189
Today I was able to have a look at it. The ztk buildouts are currently tailored for python3, I readded python 2 specific packages with two new cfgs. I'll add python 3 tests soonishly. I now have different test failures, and I can't make sense of them. http://jenkins.do3.cc/job/zopetoolkit_trunk_everycommit/70/console zope.container fails, because it cant import the persistent package. There is no persistent package in the test script of zope.container, but the new persistent package is a requirement in the setup.py of zope.container. I PDBed into compattest to find out that for some reason, buildout finds the persistent egg in the ZODB src directory. I do not know how the egg has ended there. Anybody knows which distutils or setuptools magic might be involved here? Best regards, Patrick
participants (5)
-
Adam GROSZER -
Marius Gedminas -
Patrick Gerken -
Stephan Richter -
Zope tests summarizer