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' >
[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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:15 PM, Tres Seaver wrote: > The work to create a compatible pure-Python proxy is partly done (I > added tests for all the features of the C version I could discover). > The version I have in my sandbox doesn't pass all those tests, so I > haven't pushed it. I put that work on a branch: https://github.com/zopefoundation/zope.security/tree/pure_python_proxy Likely I won't get back to it this week. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlEdTB4ACgkQ+gerLs4ltQ6OZQCfVIM/aPRd8BJkRSDEXx7wg4FM inIAnA0jSbOlTBdpi5P1CYtpUg/3dMF/ =4bBx -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 )
Re: [Zope-dev] [zopefoundation/ZODB] e7d8ca: Checkpoint of Python 3 port. Over 800 of the 897 u...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:53 AM, Marius Gedminas wrote: > Curious: was anyone notified by email about the comments I added to > the commit? I got an e-mail per comment. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlEdRtUACgkQ+gerLs4ltQ6FYQCcDKlpp1m/ZOoHZroXhqf4nR+B o9AAoJWKbQyGJymMp/a0udpqwZmsCP81 =3D6b -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 )
Re: [Zope-dev] zope.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/13/2013 05:02 PM, Tres Seaver wrote: > On 02/13/2013 11:04 AM, Tres Seaver wrote: >> On 02/12/2013 10:47 PM, Stephan Richter wrote: > >>> I saw you finished test coverage tonight for zope.security. What >>> is your timeline to do the port to Python 3? Our efforts are >>> blocked until we get zope.security going. We would be willing to >>> take a shot at the port, but you have just done all the hard work >>> writing the tests, so I do not want to steal the momentum from >>> you. > >> Now that the test coverage is in place, I plan to finish the Py3k >> conversion today, or tomorrow at the latest. > > The trunk is now Py3k-compatible. I'd like to hold off on a final > 4.0.0 release until I can think about adding PyPy support (pure > Python reference implementations of the _proxy and > _zope_security_checker stuff). > > We could push a 4.0.0 alpha if you need it installable from PyPI. Done: http://pypi.python.org/pypi/zope.security/4.0.0a1 The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlEdRcUACgkQ+gerLs4ltQ7zfACfTdED2bc7LizYEcxyno9G9guk tpEAoJ+lUfuRnqHeELRfkTBJOGEkpbW8 =HoJd -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 )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 16
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&r1=129373&r2=129372&p1=zopetoolkit/trunk/ztk-sources.cfg&p2=/zopetoolkit/trunk/ztk-sources.cfg Haha. My fault. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital 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 )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 16
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&r1=129373&r2=129372&p1=zopetoolkit/trunk/ztk-sources.cfg&p2=/zopetoolkit/trunk/ztk-sources.cfg On Thu, Feb 14, 2013 at 10:38 AM, Patrick Gerken wrote: > > > > On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas wrote: > >> On Thu, Feb 14, 2013 at 01:00:02AM +, 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 > > ___ 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 )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 16
On Thu, Feb 14, 2013 at 8:28 AM, Marius Gedminas wrote: > On Thu, Feb 14, 2013 at 01:00:02AM +, 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 ___ 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 )
