zope-tests - FAILED: 18, OK: 13
This is the summary for test reports received on the zope-tests list between 2013-03-02 00:00:00 UTC and 2013-03-03 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] Repository policy check found errors in 436 projects [2] Still Failing - zopetoolkit_trunk - Build # 190 Total languishing bugs for zope2: 0 [3] Total languishing bugs for zope: 69 [4] Total languishing bugs for zopeapp: 1 [5] Total languishing bugs for zopetoolkit: 205 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.formui_py_265_32 [9] winbot / z3c.language.switch_py_265_32 [10] winbot / z3c.pagelet_py_265_32 [11] winbot / zc.resourcelibrary_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.http_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.publication_py_265_32 [16] winbot / zope.app.renderer_py_265_32 [17] winbot / zope.browserpage_py_265_32 [18] 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 Repository policy check found errors in 436 projects https://mail.zope.org/pipermail/zope-tests/2013-March/073014.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 190 https://mail.zope.org/pipermail/zope-tests/2013-March/073013.html [3] FAILED Total languishing bugs for zope: 69 https://mail.zope.org/pipermail/zope-tests/2013-March/073011.html [4] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2013-March/073009.html [5] FAILED Total languishing bugs for zopetoolkit: 205 https://mail.zope.org/pipermail/zope-tests/2013-March/073010.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073007.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073003.html [8] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073006.html [9] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073008.html [10] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073001.html [11] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073031.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073029.html [13] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073030.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073004.html [15] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073028.html [16] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073002.html [17] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073027.html [18] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073005.html
On Mon, Mar 04, 2013 at 01:00:02AM +0000, Zope tests summarizer wrote:
[1] Repository policy check found errors in 436 projects
Contains a broken link to http://uter.gocept.com/~ctheune/report-2013-03-03T02:15:02.792640.txt (Host uter.gocept.com not found: 3(NXDOMAIN)) I suspect the script doesn't know about MOVED_TO_GITHUB and therefore complains about missing LICENCE.txt etc.
[2] Still Failing - zopetoolkit_trunk - Build # 190
Early in the build there's + ./bin/develop up -f /tmp/hudson7093928157358980278.sh: 1: ./bin/develop: not found what's that about? It doesn't seem to break the build (and the develop script is, apparently, generated later and then executed successfully). The failure is here: + ./bin/buildout -t 3 -v -c development-python.cfg While: Initializing. Error: Couldn't open /home/zope/.jenkins/jobs/zopetoolkit_trunk/workspace/development-python.cfg
[3] Total languishing bugs for zope: 69
I think it was the first time I read this summary (shame on me etc. etc.), it was rather interesting. I closed https://bugs.launchpad.net/z3c.form/+bug/1125906 ("please move to github")
[4] Total languishing bugs for zopeapp: 1 [5] Total languishing bugs for zopetoolkit: 205
I closed https://bugs.launchpad.net/zope.datetime/+bug/642474 ("please make setup.py test work"[1]), because it was fixed during the porting effort. [1] Here I use quotation marks for my paraphrasings instead of actual citations. Apologies for playing fast an loose with punctuation. There are a lot of "Turn package documentation into Sphinx style" bugs. I think a http://zope3.pov.lt/py3/ style summary page might be more useful for tracking this, but maybe that's just me. I closed https://bugs.launchpad.net/zope.interface/+bug/140875 because binary Windows eggs for zope.interface exist (and have existed for quite a while). Closed https://bugs.launchpad.net/zope.interface/+bug/911995 (class-advice decorators should fail loudly, not silently, in Python 3) because it's been fixed in 4.0.0 AFAIU. Marked https://bugs.launchpad.net/zope.interface/+bug/1090762 as incomplete because it's about zope.interface 4.0.2 and now 4.0.5 is out, and also because I don't understand what the problem is. My, those "Turn package documentation into Sphinx style" bugs aren't helpful at all. Closed https://bugs.launchpad.net/zope.sequencesort/+bug/642481 ("make setup.py test work") by applying the supplied patch. This also made tests fail under Python 3 and confirmed the recent report about the port being somewhat incomplete. tox/detox make it easy to not notice when your test setup is incorrect (e.g. no tests are run, or test failures do not cause sys.exit(1)). I tripped on this thing with zope.testrunner once. I tried to fix the tests under Python 3.[23], but got bogged down in the various TypeError: unorderable types: dict() < dict() errors. Help? Closed https://bugs.launchpad.net/zope.session/+bug/353647 ("zope.session 3.6 doesn't work on Python 2.4") because there's a comment claiming 3.6.1 fixed that. In 2009. And nobody ever contradicted. Closed https://bugs.launchpad.net/zope.structuredtext/+bug/642481 because it's been fixed. Reassigned 16 zope.testing bugs dealing with the test runner to zope.testrunner. Noticed that I cannot change the importance field of zope.testrunner's bugs (I can change it for zope.testing's bugs). *whew* That was a bit depressing.
[6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.formui_py_265_32 [10] winbot / z3c.pagelet_py_265_32
lxml
[9] winbot / z3c.language.switch_py_265_32
ImportError: No module named (zope.app.)testing
[11] 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-l9qzwt'
[12] winbot / zope.app.authentication_py_265_32
Unicode principal IDs
[13] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.publication_py_265_32
ImportError: No module named webtest
[14] winbot / zope.app.pagetemplate_py_265_32
\r\n
[16] 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.
[17] winbot / zope.browserpage_py_265_32
\r\n
[18] winbot / zope.formlib_py_265_32
Moved to github a while ago Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (2)
-
Marius Gedminas -
Zope tests summarizer