Re: [Zope-dev] zope-tests - FAILED: 41, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/15/2013 02:09 AM, Marius Gedminas wrote: I suggest we add an untrustedpython extra to zope.security that depends on zope.untrustedpython. And a zope.security.untrustedpython package that emits a deprecation warning on import time and does from zope.untrustedpython import *. I agree. I will work out what this needs today and release a 4.0.0a2. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEeSM4ACgkQ+gerLs4ltQ4mXgCfYAoo0SJnVNeIKOkpyLF7CBev OcsAnjRXx1o6rNo3E+whnn/le5hp8H+M =oglV -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 41, OK: 20
This is the summary for test reports received on the zope-tests list between 2013-02-13 00:00:00 UTC and 2013-02-14 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 # 172 [2]Still Failing - zopetoolkit_trunk - Build # 173 [3]Still Failing - zopetoolkit_trunk_app - Build # 155 [4]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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5]winbot / z3c.authenticator_py_265_32 [6]winbot / z3c.baseregistry_py_265_32 [7]winbot / z3c.breadcrumb_py_265_32 [8]winbot / z3c.contents_py_265_32 [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.jsonrpcproxy_py_265_32 [12] winbot / z3c.jsontree_py_265_32 [13] winbot / z3c.layer.ready2go_py_265_32 [14] winbot / z3c.macro_py_265_32 [15] winbot / z3c.pagelet_py_265_32 [16] winbot / z3c.pdftemplate_py_265_32 [17] winbot / z3c.sampledata_py_265_32 [18] winbot / z3c.tabular_py_265_32 [19] winbot / z3c.template_py_265_32 [20] winbot / z3c.testing_py_265_32 [21] winbot / z3c.viewtemplate_py_265_32 [22] winbot / z3c.xmlhttp_py_265_32 [23] winbot / z3c.zrtresource_py_265_32 [24] winbot / zc.catalog_py_265_32 [25] winbot / zc.table_py_265_32 [26] winbot / zope.app.authentication_py_265_32 [27] winbot / zope.app.component_py_265_32 [28] winbot / zope.app.container_py_265_32 [29] winbot / zope.app.exception_py_265_32 [30] winbot / zope.app.http_py_265_32 [31] winbot / zope.app.publisher_py_265_32 [32] winbot / zope.app.session_py_265_32 [33] winbot / zope.app.testing_py_265_32 [34] winbot / zope.app.wsgi_py_265_32 [35] winbot / zope.app.zcmlfiles_py_265_32 [36] winbot / zope.browsermenu_py_265_32 [37] winbot / zope.browserpage_py_265_32 [38] winbot / zope.mimetype_py_265_32 [39] winbot / zope.ptresource_py_265_32 [40] winbot / zope.traversing_py_265_32 [41] winbot / zope.viewlet_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 # 172 https://mail.zope.org/pipermail/zope-tests/2013-February/072294.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 173 https://mail.zope.org/pipermail/zope-tests/2013-February/072304.html [3]FAILED Still Failing - zopetoolkit_trunk_app - Build # 155 https://mail.zope.org/pipermail/zope-tests/2013-February/072295.html [4]FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072293.html [5]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072333.html [6]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072322.html [7]FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072323.html [8]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072320.html [9]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072353.html [10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072331.html [11] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072332.html [12] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072351.html [13] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072343.html [14] FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072337.html [15] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072339.html [16] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072335.html
Re: [Zope-dev] zope-tests - FAILED: 41, OK: 20
On Fri, Feb 15, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 172 https://mail.zope.org/pipermail/zope-tests/2013-February/072294.html Ignored, because Build # 173 is right there. [2]FAILED Still Failing - zopetoolkit_trunk - Build # 173 https://mail.zope.org/pipermail/zope-tests/2013-February/072304.html Error: Picked: zope.container = 3.12.0 Oh, look, Build # 174 also exists (and is also failing). Error: Picked: BTrees = 4.0.5 Okay. Here's what's happening: * Latest ZODB3 was split into independent ZODB, ZEO, BTrees, persistent, transaction packages (the latter two were split out earlier). * Bleeding edge zope.container started depending on these smaller packages instead of depending on the monolithic ZODB3. * zopetoolkit points to ZODB3/branches/3.10, i.e. before the split * I suspect that trying to develop = ZODB3 version 3.10.x and BTrees is not going to work well, since both will be trying to put 'BTrees' onto your sys.path What does the zope toolkit want to do with this? Pin zope.container to an earlier branch, maybe? [3]FAILED Still Failing - zopetoolkit_trunk_app - Build # 155 https://mail.zope.org/pipermail/zope-tests/2013-February/072295.html Build # 156 is latest and it fails with the same issue. [4]FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072293.html Haven't looked at it yet. [5]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072333.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [6]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072322.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [7]FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072323.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [8]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072320.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [9]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072353.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072331.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [11] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072332.html [12] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072351.html [13] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072343.html [14] FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072337.html [15] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072339.html [16] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072335.html [17] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072326.html [18] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072319.html [19] FAILED winbot / z3c.template_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072324.html [20] FAILED winbot / z3c.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072321.html [21] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072329.html [22] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072350.html [23] FAILED winbot / z3c.zrtresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072346.html I didn't even look. I expect they all depend on the same thing which depends on zope.security[untrustedpython]. It's annoying that buildout (or easy_install) doesn't tell you what package is declaring a dependency on the unknown extra. [24] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072338.html UnknownExtra: zope.security 4.0.0a1 has no such extra feature 'untrustedpython' [25] FAILED winbot / zc.table_py_265_32
