Re: [Zope-dev] zope-tests - FAILED: 1, OK: 8
On Tue, Oct 15, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED Failure - zopetoolkit_trunk - Build # 427 https://mail.zope.org/pipermail/zope-tests/2013-October/079244.html Network timeout while trying to connect and fetch http://python-distribute.org/distribute_setup.py (I see there are still copies of bootstrap.py that execute code fetched over plain HTTP. Don't let Donald Stufft know.) 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 )
[Zope-dev] zope-tests - FAILED: 1, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-10-13 00:00:00 UTC and 2013-10-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]Failure - zopetoolkit_trunk - Build # 427 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 Failure - zopetoolkit_trunk - Build # 427 https://mail.zope.org/pipermail/zope-tests/2013-October/079244.html ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-12 00:00:00 UTC and 2013-10-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 Successful - zopetoolkit_trunk - Build # 426 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 -- ___ 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: 1, OK: 9
On Sat, Oct 12, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079204.html The usual 24-hour winbot lag. Last build was successful. 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: 1, OK: 9
On Thu, Oct 10, 2013 at 02:19:21PM +0300, Marius Gedminas wrote: On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html I haven't found the round tuits to fix this yet. I still plan on doing that, whenever I can find the mythical spare time. Should be fixed with zope.testbrowser 4.0.4. 5.0.0 is still waiting for documentation testing and some crawling of all reverse dependencies to see how badly they break and how hard they're to fix. If any of you care about zope.testbrowser on Python 3, feel free to pitch in. 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 )
[Zope-dev] svn.zope.org issue
Hi! Where can I report problems with svn.zope.org? For some days now I have trouble making checkins. Commits are successful, but somewhere in the post commit hook things go wrong. No mail is send to the checkins list and my svn client freezes - I guess because the server doesn't signal the commit is finished. Other people seem to have the same issue, the last checkin mail to the list was sent 2013-09-17. Cheers, Yuppie ___ 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] svn.zope.org issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/11/2013 08:21 AM, yuppie wrote: Hi! Where can I report problems with svn.zope.org? For some days now I have trouble making checkins. Commits are successful, but somewhere in the post commit hook things go wrong. No mail is send to the checkins list and my svn client freezes - I guess because the server doesn't signal the commit is finished. Other people seem to have the same issue, the last checkin mail to the list was sent 2013-09-17. The ZF infrastructure committee is working on moving SVN to a new host. Report problems to infrastruct...@zope.org. 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJYMb0ACgkQ+gerLs4ltQ7SKwCgmACy6IPOT1eCX/LTIs2lcLQC 22sAoL2rCgelzJ9hd3BDhE8NQBj+BbfA =/Wgl -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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-10 00:00:00 UTC and 2013-10-11 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 Successful - zopetoolkit_trunk - Build # 424 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079204.html ___ 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: 1, OK: 9
On Thu, Oct 10, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html I haven't found the round tuits to fix this yet. I still plan on doing that, whenever I can find the mythical spare time. 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 )
[Zope-dev] zope-tests - FAILED: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-09 00:00:00 UTC and 2013-10-10 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 Successful - zopetoolkit_trunk - Build # 423 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079187.html ___ 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: 1, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/08/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079153.html Transient github failure: fatal: unable to connect to github.com: github.com[0: 192.30.252.131]: errno=No such file or directory 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJVnpwACgkQ+gerLs4ltQ5XZgCeIfK/wW6o97VFMRhtroymGOHl 2hEAnRtLOmPoaibbkYnl5nXrCCm7BcRK =IVBr -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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-08 00:00:00 UTC and 2013-10-09 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 Successful - zopetoolkit_trunk - Build # 422 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079170.html ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-06 00:00:00 UTC and 2013-10-07 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 Successful - zopetoolkit_trunk - Build # 420 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 -- ___ 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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-05 00:00:00 UTC and 2013-10-06 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 Successful - zopetoolkit_trunk - Build # 419 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079118.html ___ 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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-04 00:00:00 UTC and 2013-10-05 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 Successful - zopetoolkit_trunk - Build # 418 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079101.html ___ 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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-03 00:00:00 UTC and 2013-10-04 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 Successful - zopetoolkit_trunk - Build # 417 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079084.html ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-02 00:00:00 UTC and 2013-10-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 Successful - zopetoolkit_trunk - Build # 416 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 -- ___ 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: 1, OK: 9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/01/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079033.html Failure in buildout phase:: Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.9 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlJMdroACgkQ+gerLs4ltQ5MDgCdF5E7uAlCblkYBLgLjfJGf2du 4PAAoKHbJUGLQzUEhzH8EdWN8iaPNHVv =y37n -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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-10-01 00:00:00 UTC and 2013-10-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 Successful - zopetoolkit_trunk - Build # 415 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 -- ___ 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] (optional) CSRF protection in zope.formlib
On 9/18/13 4:41 PM, Jan-Wijbrand Kolman wrote: I've been working on CSRF protection for zope.formlib. Anyone else interested in this feature? We made an internal release of zope.formlib with this functionality and so far we found no issues in using it in production. After updating zope.formlib's tests to also run on Python 3, I could merge this feature soon. Unless of course, someone objects :-) kind regards, jw ___ 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: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-30 00:00:00 UTC and 2013-10-01 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 Successful - zopetoolkit_trunk - Build # 414 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-October/079033.html ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-29 00:00:00 UTC and 2013-09-30 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 Successful - zopetoolkit_trunk - Build # 413 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 -- ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-28 00:00:00 UTC and 2013-09-29 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 Successful - zopetoolkit_trunk - Build # 412 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 -- ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-27 00:00:00 UTC and 2013-09-28 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 Successful - zopetoolkit_trunk - Build # 411 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 -- ___ 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: 5, OK: 9
On Fri, Sep 27, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]FAILED winbot / zc.ngi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078948.html
Intermittent error. An interesting one:
--
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.test, line 253, in async.test
Failed example:
zc.ngi.async.cleanup_map()
Exception raised:
Traceback (most recent call last):
File c:\Python26_32\lib\doctest.py, line 1253, in __run
compileflags, 1) in test.globs
File doctest async.test[64], line 1, in module
zc.ngi.async.cleanup_map()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 175, in
cleanup_map
c.close()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 707, in close
self.implementation.call_from_thread(lambda : self._close(handler))
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 69, in
call_from_thread
self.notify_select()
File c:\buildslave\zc.ngi\build\src\zc\ngi\async.py, line 882, in
pull_trigger
self.trigger.send('x')
File c:\Python26_32\lib\socket.py, line 167, in _dummy
raise error(EBADF, 'Bad file descriptor')
error: [Errno 9] Bad file descriptor
--
[2]FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078945.html
[3]FAILED winbot / zope.app.http_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078946.html
[4]FAILED winbot / zope.app.publication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078944.html
[5]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078947.html
WebTest version conflict.
(I'll get to it at some point, but ATM I'm busy.)
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 )
[Zope-dev] zope-tests - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-26 00:00:00 UTC and 2013-09-27 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 Successful - zopetoolkit_trunk - Build # 410 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 -- ___ 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: 5, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-25 00:00:00 UTC and 2013-09-26 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 Successful - zopetoolkit_trunk - Build # 409 [1]winbot / zc.ngi_py_265_32 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.wsgi_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 winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078948.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078945.html [3]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078946.html [4]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078944.html [5]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078947.html ___ 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: 1, OK: 9
On Wed, Sep 25, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078913.html Ah, the webtest version conflict is back. 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 )
[Zope-dev] zope-tests - FAILED: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-24 00:00:00 UTC and 2013-09-25 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 Successful - zopetoolkit_trunk - Build # 408 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078930.html ___ 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: 1, OK: 7
On Tue, Sep 24, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote: [1]FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-September/078904.html File c:\eggs\zope.testrunner-4.0.4-py2.7.egg\zope\testrunner\testrunner-layers-buff.txt, line 100, in testrunner-layers-buff.txt The 'LAYER FINISHED' text appears at a latter point than expected. Looks like a slight race condition in the test. 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 )
[Zope-dev] zope-tests - FAILED: 1, OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-23 00:00:00 UTC and 2013-09-24 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 Successful - zopetoolkit_trunk - Build # 407 [1]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078913.html ___ 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: 12, OK: 8
On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote: On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 zope.testbrowser-caused WebTest version conflict. I've no idea why these errors disappeared. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). I basically chickened out. IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package). What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (=4.x) to newer versions (5.x). I will not do a release until this documentation exists. It may take me some time to find the time and remember how everything fits together. It shouldn't be too hard (just find some zope package that did the migration in a py3 branch, then document what it did), but I find my motivation is pretty low this week. 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: 12, OK: 8
On 09/23/2013 10:03 AM, Marius Gedminas wrote: On Fri, Sep 13, 2013 at 09:01:37AM +0300, Marius Gedminas wrote: On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 zope.testbrowser-caused WebTest version conflict. I've no idea why these errors disappeared. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). I basically chickened out. IIRC the new webtest-based zope.testbrowser breaks API pretty hard (e.g. you can't use zope.app.testing.functional.FunctionalTestLayer any more; you must create a WSGITestLayer from I-forgot-what-zope.-package). What's worse, it lacks documentation for how you're supposed to migrate from older zope.testbrowser versions (=4.x) to newer versions (5.x). I will not do a release until this documentation exists. Could you add a line to let's say CHANGES.txt about this? The idea would be to really block a release. Not that someone comes around and pushes the release out half baked. -- Best regards, Adam GROSZER -- Quote of the day: It is never worthwhile to make rents in a garment for the sake of mending them? Nor to create doubts in order to show how cleverly we can quiet them. - Charles Haddon Spurgeon ___ 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: 1, OK: 7
This is the summary for test reports received on the zope-tests list between 2013-09-22 00:00:00 UTC and 2013-09-23 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 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 [1]winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED winbot / ztk_11 py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-September/078904.html ___ 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] please move z3c.formwidget.query to github
Hi, Can someone please migrate z3c.formwidget.query to github? This package is a dependency of plone.formwidget.autocomplete and I need to make a fix. This is broken since z3c.form = 2.6.0 which remove :list suffix from radiobox. See the attached patch. Vincent Fretin Ecreall http://www.ecreall.com z3c.formwidget.query_radio_novalue_fix.patch Description: Binary data ___ 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] please move z3c.formwidget.query to github
I thought the zope svn was read-only, but I actually succeeded to do the commit. Can someone please make a new release? Thanks. Vincent On Sun, Sep 22, 2013 at 5:22 PM, Vincent Fretin vincent.fre...@gmail.comwrote: Hi, Can someone please migrate z3c.formwidget.query to github? This package is a dependency of plone.formwidget.autocomplete and I need to make a fix. This is broken since z3c.form = 2.6.0 which remove :list suffix from radiobox. See the attached patch. Vincent Fretin Ecreall http://www.ecreall.com ___ 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] please move z3c.formwidget.query to github
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/22/2013 11:27 AM, Vincent Fretin wrote: Can someone please make a new release? Releases can be made only by one of: malthe, optilude, davisagli, laurencerowe, timo, esteele - -- === 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI/M3YACgkQ+gerLs4ltQ4aIQCeLTrcoCxUzDe3M3c98y9t4DmS LzYAoNWgpyb1W/LEXYDzWiWWZPD4YaHj =HrN6 -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 - OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-21 00:00:00 UTC and 2013-09-22 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 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 -- ___ 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: 1, OK: 8
On Sat, Sep 21, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / zope.testbrowser_py_265_32 Last build was successful. 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 )
[Zope-dev] zope-tests - OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-20 00:00:00 UTC and 2013-09-21 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 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 -- ___ 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 - OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/21/2013 07:00 PM, Zope tests summarizer wrote: This is the summary for test reports received on the zope-tests list between 2013-09-20 00:00:00 UTC and 2013-09-21 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 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 Yay! 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 Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlI+Tq4ACgkQ+gerLs4ltQ57JQCfaojpXeeQCmMFhuAb5etsoePS zm0AnR8Q3FYxrsqnfUFu6V/VVU9KxPH0 =ztKD -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: 6, OK: 12
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/18/2013 06:40 AM, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. FWIW, WebTest 2.0.9 went out Wednesday: https://pypi.python.org/pypi/WebTest/2.0.9 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/ iEYEARECAAYFAlI8UDAACgkQ+gerLs4ltQ7ElgCePY2PC6fHHpf9p/jZAXWZdYe5 ThMAoIyTyVjI8PzbERIPVKMpKhK4KTop =Gnik -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: 6, OK: 12
On Fri, Sep 20, 2013 at 09:40:00AM -0400, Tres Seaver wrote: On 09/18/2013 06:40 AM, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. FWIW, WebTest 2.0.9 went out Wednesday: https://pypi.python.org/pypi/WebTest/2.0.9 Thank you, I didn't notice. Pushed a test fix (zope.testbrowser actually had a test that asserted the content type we specified was being ignored!). 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 )
[Zope-dev] zope-tests - FAILED: 1, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-19 00:00:00 UTC and 2013-09-20 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]winbot / zope.testbrowser_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 winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078849.html ___ 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] github etiquette
Op 17-09-13 17:15, Marius Gedminas schreef: On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote: FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. Sorry, I don't understand the point you're making. I'll try to explain better. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) So are you saying you don't merge other people's code because you don't want to ask if they're contributors? No. I'm saying the reviewer-merges workflow looks like this: 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer asks have you signed the agreement? if not please sign 5. OP says he/she signed it 6. Reviewer trusts OP's word and merges (I don't have a good short word for somebody who created the pull request, so I abused Original Poster.) Whereas I'd prefer 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer says looks good to me, feel free to merge (if you're not a committer already, see http://foundation.zope.org/agreements) 5. OP merges It's not a very strong preference. I can feel myself changing my mind already ;-) OTOH the implicit trust in step 6 makes me a bit uneasy, and I'm not quite sure how to verify the fact of the signing. Wait for the user to show up in https://github.com/zopefoundation?tab=members ? Checking that list seems the best to me. This could be a reason to prefer that the 'pull requester' creates a branch in the original repository within the zopefoundation: if he can do that, it proves he is authorized and has signed the agreement. BTW, I have just now seen that I am on that list in the members tab, but in the greyed out section, which I think means that non-members do not see me listed. There was a button 'Publicize membership' next to my name so I clicked and am now in the top 'full-color' list. :-) Others may want to do the same. -- Maurits van Rees: http://maurits.vanrees.org/ Zest Software: http://zestsoftware.nl ___ 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: 5, OK: 10
This is the summary for test reports received on the zope-tests list between 2013-09-18 00:00:00 UTC and 2013-09-19 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 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_py_265_32 [5]winbot / zope.testbrowser_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078829.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078830.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078828.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078831.html [5]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078832.html ___ 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: 6, OK: 12
On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / ZODB_dev py_265_win64 Non-deterministic test failure: Failure in test c:\buildslave\zodb_dev_py_265_win64\build\src\ZODB\historical_connections.txt -- File c:\buildslave\zodb_dev_py_265_win64\build\src\ZODB\historical_connections.txt, line 220, in historical_connections.txt Failed example: [c in conns1 for c in conns2] Expected: [False, False, True, True] Got: [False, False, False, True] Cleared up all by itself on next build. [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.wsgi_py_265_32 WebTest version conflict [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 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: 6, OK: 12
On Wed, Sep 18, 2013 at 11:11:50AM +0300, Marius Gedminas wrote: On Wed, Sep 18, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [6]winbot / zope.testbrowser_py_265_32 The fix that was supposed to fix this didn't because https://github.com/Pylons/webtest/pull/87/files#r6427276 We're waiting for https://github.com/Pylons/webtest/pull/88 and WebTest 2.0.9 now. 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 )
[Zope-dev] (optional) CSRF protection in zope.formlib
Hi, I've been working on CSRF protection for zope.formlib. I have a csrfprotection branch in my zope.formlib fork on github. The changes against the current zope.formlib mainline can be found here: https://github.com/janwijbrand/zope.formlib/compare/csrfprotection When creating form components based on zope.formlib.form.FormBase, one can enable this protection just by setting the attribute ``protected`` to True on the component. This implementation is based on the following assumptions: * We do not want to keep server-side state(!) * An attacker that attempts CSRF cannot get to information stored in cookies that are meant for the domain of the (forged) request. * The token stored in the cookie is sufficiently random and long, to be practically unguessable by the attacker. * The form submit is deemed valid as long as the token in the cookie is identical to a hidden input value that is part of the form submit. My questions: * Do you find this feature useful enough to be, in principle, included in zope.formlib? * I'd like to kindly request someone to review my branch and provide feedback. The included test cases describe a few more questions and concerns about this implementation. Thank you in advance! kind regards, jw ___ 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] (optional) CSRF protection in zope.formlib
Hi Jan-Wij, +1 for implementing convenient CSRF. I wonder if you could make your implementation more orthogonal by implementing a CSRF field/widget, and make your `protected` attribute simply trigger the inclusion of this field implicitly. This way you wouldn't need to change the `*pageform.pt` templates like you do now, and `setupToken()`/`checkToken()` would move to the widget code. Cheers, Leo On Wed, Sep 18, 2013 at 11:41 AM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: Hi, I've been working on CSRF protection for zope.formlib. I have a csrfprotection branch in my zope.formlib fork on github. The changes against the current zope.formlib mainline can be found here: https://github.com/**janwijbrand/zope.formlib/**compare/csrfprotectionhttps://github.com/janwijbrand/zope.formlib/compare/csrfprotection When creating form components based on zope.formlib.form.FormBase, one can enable this protection just by setting the attribute ``protected`` to True on the component. This implementation is based on the following assumptions: * We do not want to keep server-side state(!) * An attacker that attempts CSRF cannot get to information stored in cookies that are meant for the domain of the (forged) request. * The token stored in the cookie is sufficiently random and long, to be practically unguessable by the attacker. * The form submit is deemed valid as long as the token in the cookie is identical to a hidden input value that is part of the form submit. My questions: * Do you find this feature useful enough to be, in principle, included in zope.formlib? * I'd like to kindly request someone to review my branch and provide feedback. The included test cases describe a few more questions and concerns about this implementation. Thank you in advance! kind regards, jw __**_ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/**listinfo/zope-devhttps://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/**listinfo/zope-announcehttps://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/**listinfo/zopehttps://mail.zope.org/mailman/listinfo/zope) ___ 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] (optional) CSRF protection in zope.formlib
On 9/18/13 5:26 PM, Leonardo Rochael Almeida wrote: +1 for implementing convenient CSRF. I wonder if you could make your implementation more orthogonal by implementing a CSRF field/widget, and make your `protected` attribute simply trigger the inclusion of this field implicitly. This way you wouldn't need to change the `*pageform.pt http://pageform.pt` templates like you do now, and `setupToken()`/`checkToken()` would move to the widget code. I've considered and experimented with that approach. However, as soon as you do more complex things with setting up fields in your own form component, things potentially get hairy. Furthermore, the form machinery tries to get values from the context object (in edit forms for example), for each field and tries to set values for this field on the context object when handling the submit. This would make handling this field special in way I didn't like. But yes, the compromise in my implementation is, that you need to render the hidden input field yourself if you overwrite the default templates - and you most probably do. For example, grok.formlib does bring its own default templates for forms. I'd need to update that package in case this implementation is accepted and lands. regards, jw ___ 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: 5, OK: 13
This is the summary for test reports received on the zope-tests list between 2013-09-17 00:00:00 UTC and 2013-09-18 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 Successful - zopetoolkit_trunk - Build # 406 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_py_265_32 [5]winbot / zope.testbrowser_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078812.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078813.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078811.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078814.html [5]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078815.html ___ 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] github etiquette
Hi, I wonder if there is a formal or informal write-up of how to nicely contribute code to the repositories under the zopefoundation umbrella. Back in the subversion days I would branch a project, amend code, write tests, commit this to the repository, ask for feedback on the list, and, when deemed acceptable, merge my changes back to the project's trunk, perhaps even make a release of the project. Yesterday I wanted to add a small feature to zope.formlib and wondered whether I should: 1) clone the canonical zope.formlib repository, make a branch, do my work, push the changes, ask for feedback on the list and eventually merge the branch to the mainline. or 2) fork the repository, make a branch in the fork, do my work, push the changes to my fork, and issue a pull request. The latter is what I did, without explicitly asking for feedback. Luckily someone did give me feedback (thanks!) :-) Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? My apologies in case I missed an obvious document or reference somewhere that describes the way we should work with the zopefoundation's codebase... kind regards, jw ___ 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] github etiquette
On Tue, Sep 17, 2013 at 12:04:04PM +0200, Jan-Wijbrand Kolman wrote: I wonder if there is a formal or informal write-up of how to nicely contribute code to the repositories under the zopefoundation umbrella. I don't think so. I'd like to see one. Back in the subversion days I would branch a project, amend code, write tests, commit this to the repository, ask for feedback on the list, and, when deemed acceptable, merge my changes back to the project's trunk, perhaps even make a release of the project. Yesterday I wanted to add a small feature to zope.formlib and wondered whether I should: 1) clone the canonical zope.formlib repository, make a branch, do my work, push the changes, ask for feedback on the list and eventually merge the branch to the mainline. or 2) fork the repository, make a branch in the fork, do my work, push the changes to my fork, and issue a pull request. The latter is what I did, without explicitly asking for feedback. Luckily someone did give me feedback (thanks!) :-) I think a pull request is right. It doesn't matter much if the branch you're asking to pull is in the main repository or in a private fork. Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) My apologies in case I missed an obvious document or reference somewhere that describes the way we should work with the zopefoundation's codebase... Can we please get the http://foundation.zope.org/ website source on GitHub, so it becomes maintainable by the community? 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] github etiquette
On 9/17/13 12:04 PM, Jan-Wijbrand Kolman wrote: snip 2) fork the repository, make a branch in the fork, do my work, push the changes to my fork, and issue a pull request. The latter is what I did, without explicitly asking for feedback. Luckily someone did give me feedback (thanks!) :-) Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? This is what I did just now. Kind regards, jw ___ 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] github etiquette
On 9/17/13 1:00 PM, Marius Gedminas wrote: On Tue, Sep 17, 2013 at 12:04:04PM +0200, Jan-Wijbrand Kolman wrote: I wonder if there is a formal or informal write-up of how to nicely contribute code to the repositories under the zopefoundation umbrella. I don't think so. I'd like to see one. I think we're writing it Right Now :-) regards, jw ___ 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] github etiquette
On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote: ... 2) fork the repository, make a branch in the fork, do my work, push the changes to my fork, and issue a pull request. The latter is what I did, without explicitly asking for feedback. Luckily someone did give me feedback (thanks!) :-) I think a pull request is right. Yup. It doesn't matter much if the branch you're asking to pull is in the main repository or in a private fork. Yup. (Apparently, number of forks is a way some people keep score on github, so I'll cynically say a fork is better.) Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) I strongly prefer that the reviewer do the merge. I'd also really like reviewers to take their responsibility seriously, making comments and suggestions where appropriate. Software review, done well, improves the software, and, more importantly, improves the developers. My apologies in case I missed an obvious document or reference somewhere that describes the way we should work with the zopefoundation's codebase... Can we please get the http://foundation.zope.org/ website source on GitHub, so it becomes maintainable by the community? Oh yes, please! Unfortunately, this will require moving from silva to sphinx. It will also entail separating the public sites from private documents. (The above isn't meant to dis silva, it's just not a good fit for zopefoundation.org.) Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ 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] github etiquette
On 9/17/13 1:47 PM, Jim Fulton wrote: I strongly prefer that the reviewer do the merge. I'd also really like reviewers to take their responsibility seriously, making comments and suggestions where appropriate. Software review, done well, improves the software, and, more importantly, improves the developers. I agree - I know I get better from recieving feedback :-) Is this reviewer role something someone takes upon himself? I mean, if I see a pull request for a code base that I know, I could review the request? Or do we acknowledge a group of people that generally do reviews (again formally of informally, I don't mind, I'm not looking for official procedures)? In any case, a second pair of eyes before merging is very helpful! regards, jw p.s. Another thing I noticed: some of the discussion about changes and patches and fixes now shift from the mailinglist to github. This is fine, I guess. ___ 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] github etiquette
On Tue, Sep 17, 2013 at 07:47:42AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote: Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) I strongly prefer that the reviewer do the merge. FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) I'd also really like reviewers to take their responsibility seriously, making comments and suggestions where appropriate. Oh, absolutely. Software review, done well, improves the software, and, more importantly, improves the developers. 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] github etiquette
On Tue, Sep 17, 2013 at 8:32 AM, Jan-Wijbrand Kolman janwijbr...@gmail.com wrote: On 9/17/13 1:47 PM, Jim Fulton wrote: I strongly prefer that the reviewer do the merge. I'd also really like reviewers to take their responsibility seriously, making comments and suggestions where appropriate. Software review, done well, improves the software, and, more importantly, improves the developers. I agree - I know I get better from recieving feedback :-) Is this reviewer role something someone takes upon himself? I mean, if I see a pull request for a code base that I know, I could review the request? These are good questions. I probably don't have satisfying answers. The short answer is that I think people who contribute to a project should view review as one of their duties. For better or worse, this is somewhat informal. If you don't get a review in a timely manner, try posting to the appropriate mailing list to request a review. Or do we acknowledge a group of people that generally do reviews (again formally of informally, I don't mind, I'm not looking for official procedures)? No. p.s. Another thing I noticed: some of the discussion about changes and patches and fixes now shift from the mailinglist to github. This is fine, I guess. Yes, IMO. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ 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] github etiquette
On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote: On Tue, Sep 17, 2013 at 07:47:42AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 7:00 AM, Marius Gedminas mar...@gedmin.as wrote: Now that I mended the pull request, should I merge the pull request myself? Or is the current etiquette that someone else should merge the pull request? I think it's fine to merge own pull requests, provided that somebody +1'd it. (Or if nobody cared for a couple of weeks, even after asking for feedback on the list.) I strongly prefer that the reviewer do the merge. FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. Sorry, I don't understand the point you're making. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) So are you saying you don't merge other people's code because you don't want to ask if they're contributors? I can understand this, but I'd still try to encourage a more review-centric workflow. Also, if a change is trivial, the PR doesn't have to be from a contributor. I understand that triviality isn't always clear. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton ___ 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] github etiquette
On 9/17/13 3:32 PM, Jim Fulton wrote: On Tue, Sep 17, 2013 at 8:32 AM, Jan-Wijbrand Kolman Is this reviewer role something someone takes upon himself? I mean, if I see a pull request for a code base that I know, I could review the request? These are good questions. I probably don't have satisfying answers. The short answer is that I think people who contribute to a project should view review as one of their duties. For better or worse, this is somewhat informal. If you don't get a review in a timely manner, try posting to the appropriate mailing list to request a review. Works for me :-) regards, jw ___ 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] Misattribution of checkin emails
Certain Subversion commits show up on the checkins@ list misattributed to Marius Gedminas cvs-ad...@zope.org. Examples: r130062 - https://mail.zope.org/pipermail/checkins/2013-March/065903.html r130296 - https://mail.zope.org/pipermail/checkins/2013-August/067498.html r130309 - https://mail.zope.org/pipermail/checkins/2013-September/067596.html All of these were actually made by Gediminas Paulauskas (svn username 'menesis'). I've tried to raise this on the checkins@ list but received no response yet. 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] github etiquette
On Tue, Sep 17, 2013 at 09:35:58AM -0400, Jim Fulton wrote: On Tue, Sep 17, 2013 at 8:58 AM, Marius Gedminas mar...@gedmin.as wrote: FWIW the only reason I'm in favour of self-merges is that this short-circuits the have you signed the ZF committer agreement? dance. Only people who have can merge. Sorry, I don't understand the point you're making. I'll try to explain better. I also feel silly when I ask this question from people with very familiar names. (I feel that I have to do when I don't see ZF membership on their GitHub profile.) So are you saying you don't merge other people's code because you don't want to ask if they're contributors? No. I'm saying the reviewer-merges workflow looks like this: 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer asks have you signed the agreement? if not please sign 5. OP says he/she signed it 6. Reviewer trusts OP's word and merges (I don't have a good short word for somebody who created the pull request, so I abused Original Poster.) Whereas I'd prefer 1. Somebody creates a pull request 2. A reviewer reviews 3. OP fixes 4. Reviewer says looks good to me, feel free to merge (if you're not a committer already, see http://foundation.zope.org/agreements) 5. OP merges It's not a very strong preference. I can feel myself changing my mind already ;-) OTOH the implicit trust in step 6 makes me a bit uneasy, and I'm not quite sure how to verify the fact of the signing. Wait for the user to show up in https://github.com/zopefoundation?tab=members ? I can understand this, but I'd still try to encourage a more review-centric workflow. +1 Also, if a change is trivial, the PR doesn't have to be from a contributor. I understand that triviality isn't always clear. It's completely unclear to me, once the PR goes beyond typo fixes. :( 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 )
[Zope-dev] zope-tests - FAILED: 6, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-09-16 00:00:00 UTC and 2013-09-17 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 Successful - zopetoolkit_trunk - Build # 405 winbot / ZODB_dev py_265_win32 [1]winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.wsgi_py_265_32 [6]winbot / zope.testbrowser_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 winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-September/078789.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078794.html [3]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078795.html [4]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078793.html [5]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078796.html [6]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078797.html ___ 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: 5, OK: 12
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot / zope.testbrowser_py_265_32
Interesting new error:
Failure in test test_file_upload (zope.testbrowser.tests.test_browser)
Failed doctest test for zope.testbrowser.tests.test_browser.test_file_upload
File
c:\buildslave\zope.testbrowser\build\src\zope\testbrowser\tests\test_browser.py,
line 324, in test_file_upload
--
File
c:\buildslave\zope.testbrowser\build\src\zope\testbrowser\tests\test_browser.py,
line 358, in zope.testbrowser.tests.test_browser.test_file_upload
Failed example:
browser.getControl('OK').click() # doctest: +REPORT_NDIFF +ELLIPSIS
Differences (ndiff with -expected +actual):
POST / HTTP/1.1
- ...
- Content-disposition: form-data; name=foo; filename=x.csv
- Content-type: text/csv
+ Connection: close
+ Host: localhost
+ Referer: http://localhost/
+ User_Agent: Python-urllib/2.4
+ X_Zope_Handle_Errors: True
BLANKLINE
+ --
+ Content-disposition: form-data; name=foo; filename=x.csv
+ Content-type: application/octet-stream
+
- blah blah blah
+ blah blah blah
? +
- ...
+ --
+ BLANKLINE
Ran 39 tests with 1 failures, 0 errors and 0 skipped in 1.328 seconds.
At first I suspected Windows line endings, but look closer:
- Content-type: text/csv
+ Content-type: application/octet-stream
Any ideas?
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: 5, OK: 12
On Mon, Sep 16, 2013 at 01:50:32PM +0300, Marius Gedminas wrote:
On Mon, Sep 16, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[5]winbot / zope.testbrowser_py_265_32
Interesting new error:
...
At first I suspected Windows line endings, but look closer:
- Content-type: text/csv
+ Content-type: application/octet-stream
rdesktop winbot.zope.org
Git Bash
$ /c/python26_32/python
import mimetypes
mimetypes.guess_type('x.csv')
(None, None)
So that's fun.
The test in question does
browser.getControl(name='foo').add_file(
... b'blah blah blah', 'text/csv', 'x.csv')
and then we get to the implementation of .add_file(), which has this
nice little XXX comment
# XXX: webtest relies on mimetypes.guess_type to get mime type of
# upload file and doesn't let to set it explicitly, so we are ignoring
# content_type parameter here. If it is still unacceptable, consider
# using mock.object to force mimetypes to return right type.
self._form[self.name] = webtest.forms.Upload(filename or '', contents)
and then ignores the content_type argument.
First of all, monkey-patch? Instead of fixing the problem upstream?
Seriously?
Therefore https://github.com/Pylons/webtest/issues/86
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 4.0 roadmap release plan
On Sat, Sep 14, 2013, at 0:38, Baiju M wrote: Is there any roadmap release plan for Zope 4.0 ? I'm not aware on anyone still working on Zope 4. The project might come back to life at some point, but for the past couple of months it's been very quiet. At my work, we use Zope 2.12 and we are looking forward to upgrading to Zope 2.13. Depending on Zope 4.0 availability, we can think about directly moving to Zope 4.0 Zope 2.13 should be an easy upgrade. You can also selectively upgrade to DateTime 3 (huge memory savings) and Products.ZCatalog 3 (support for not queries and sort_on with multiple indexes). Note that security support for Zope 2.12 (and Python 2.6) ends in October, so upgrading is a good idea. Hanno ___ 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: 5, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-09-15 00:00:00 UTC and 2013-09-16 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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_py_265_32 [5]winbot / zope.testbrowser_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078776.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078777.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078775.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078778.html [5]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078779.html ___ 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: 5, OK: 13
On Sun, Sep 15, 2013 at 01:00:01AM +0200, Zope tests summarizer wrote:
[1]winbot / zope.app.authentication_py_265_32
[2]winbot / zope.app.http_py_265_32
[3]winbot / zope.app.publication_py_265_32
[4]winbot / zope.app.wsgi_py_265_32
WebTest version conflict
[5]winbot / zope.testbrowser_py_265_32
This is new: bootstrap.py fails with
Traceback (most recent call last):
File bootstrap.py, line 108, in module
pkg_resources.Requirement.parse('distribute')).location
AttributeError: 'NoneType' object has no attribute 'location'
Last successful buildi (commit b0ed26c):
http://winbot.zope.org/builders/zope.testbrowser_py_265_32/builds/988
First failing build: commit c68904b.
What happened in between: I merged the py3 branch into master.
Old master used buildout 1.x. The py3 branch used buildout 2.0.
I'll try updating bootstrap.py to v2.2.
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 )
[Zope-dev] zope-tests - FAILED: 5, OK: 12
This is the summary for test reports received on the zope-tests list between 2013-09-14 00:00:00 UTC and 2013-09-15 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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_py_265_32 [5]winbot / zope.testbrowser_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078759.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078760.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078758.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078761.html [5]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078762.html ___ 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: 5, OK: 13
This is the summary for test reports received on the zope-tests list between 2013-09-13 00:00:00 UTC and 2013-09-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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [1]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_py_265_32 [5]winbot / zope.testbrowser_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 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078742.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078743.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078741.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078744.html [5]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078745.html ___ 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: 12, OK: 8
On Fri, Sep 13, 2013 at 01:00:02AM +0200, Zope tests summarizer wrote: [1]winbot / z3c.ptcompat_py_265_32 [5]winbot / zope.app.publisher_py_265_32 [6]winbot / zope.app.security_py_265_32 [7]winbot / zope.app.session_py_265_32 [9]winbot / zope.catalog_py_265_32 [10] winbot / zope.exceptions_py_265_32 [11] winbot / zope.session_py_265_32 [12] winbot / zope.viewlet_py_265_32 GitHub was unreachable: fatal: unable to connect to github.com: github.com[0: 192.30.252.130]: errno=No such file or directory Ironically, https://status.github.com/ is giving me a 500 Internal Server Error right now. a few minutes later It's back up and shows no downtime during the last 7 days. Must be a network problem. [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 zope.testbrowser-caused WebTest version conflict. I plan to release zope.testbrowser 5.0.0 this week. It should fix these (and probably cause lots of pain elsewhere, if people use undocumented internals like .mech_browser directly, which they do). 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 )
[Zope-dev] Zope 4.0 roadmap release plan
Hi, Is there any roadmap release plan for Zope 4.0 ? At my work, we use Zope 2.12 and we are looking forward to upgrading to Zope 2.13. Depending on Zope 4.0 availability, we can think about directly moving to Zope 4.0 Regards, Baiju M ___ 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: 6, OK: 7
This is the summary for test reports received on the zope-tests list between 2013-09-12 00:00:00 UTC and 2013-09-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 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [1]winbot / ZODB_dev py_270_win64 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.wsgi_py_265_32 [6]winbot / zope.testbrowser_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 Non-OK results -- [1]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-September/078723.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078725.html [3]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078726.html [4]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078724.html [5]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078727.html [6]FAILED winbot / zope.testbrowser_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078728.html ___ 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: 4, OK: 8
On Tue, Sep 10, 2013 at 09:49:50AM +0200, Brian Sutherland wrote: On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote: IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.) Indeed, and it's had no changes for at least 5 months and been tested with a few existing codebases. +1 for releasing it One tests fails in the py3 branch: test_strip_linebreaks_from_textarea. It tests that if you inspect getControl(name='textarea').value, you'll see one initial '\n' stripped away. This fails when the textarea in question has two initial newlines: textarea Foo /textarea The test expects .value to be '\nFoo\n', but it actually gets 'Foo\n'. This test was added by Benji York in 2006 (commit 4545f144) and refers to issue 644 in some unspecified bug tracker. Google allowed me to find a copy of the issue in question: https://bugs.launchpad.net/zope3/+bug/98371 In particular the following comment is interesting: We've verified that browsers (we tested Firefox, Mozilla, Safari, and IE) will strip a single leading newline (crlf) if it is at the beginning of the string. -- Jim Fulton, https://bugs.launchpad.net/zope3/+bug/98371/comments/12 It was serious enough to warrant changes to the local copy of ClientForm (and an upstream submission of the patch). It looks like what happened here was that WebTest itself was modified to eat the first newline in a textarea: https://github.com/Pylons/webtest/pull/69 so now we eat two. This change was released in WebTest 2.0.6: http://webtest.pythonpaste.org/en/latest/changelog.html#id2 I guess what we have to do is remove the 1st newline stripping logic from zope.testbrowser and require WebTest = 2.0.6. Ok, fixed. 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: 4, OK: 8
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support,
built on top of WebTest, waiting in the py3 branch for... Actually, I'm
not sure what it is waiting for. (I thought ZODB with Python 3 support,
but it doesn't look like zope.testbrowser depends on ZODB, at least not
directly.)
I think I remembered now: a WebTest release with some bugfixes.
I'm trying to merge the py3 branch to master now. There's one issue:
the test for https://github.com/zopefoundation/zope.testbrowser/pull/4
uses the internal .mech_browser attribute.
I think what is actually wanted here is a new API:
browser.handleRedirects = False
browser.open(...) # or browser.submit()
assert browser.getHeaders('Status') == '302 Found'
Comments?
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: 4, OK: 8
On Thursday, September 12, 2013 11:38:16 AM Marius Gedminas wrote:
m trying to merge the py3 branch to master now. There's one issue:
the test for https://github.com/zopefoundation/zope.testbrowser/pull/4
uses the internal .mech_browser attribute.
I think what is actually wanted here is a new API:
browser.handleRedirects = False
browser.open(...) # or browser.submit()
assert browser.getHeaders('Status') == '302 Found'
Comments?
+1 That looks good.
Regards,
Stephan
--
Entrepreneur and Software Geek
Google me. Zope Stephan Richter
___
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: 12, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-11 00:00:00 UTC and 2013-09-12 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]winbot / z3c.ptcompat_py_265_32 [2]winbot / zope.app.authentication_py_265_32 [3]winbot / zope.app.http_py_265_32 [4]winbot / zope.app.publication_py_265_32 [5]winbot / zope.app.publisher_py_265_32 [6]winbot / zope.app.security_py_265_32 [7]winbot / zope.app.session_py_265_32 [8]winbot / zope.app.wsgi_py_265_32 [9]winbot / zope.catalog_py_265_32 [10] winbot / zope.exceptions_py_265_32 [11] winbot / zope.session_py_265_32 [12] 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 winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078710.html [2]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078701.html [3]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078702.html [4]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078700.html [5]FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078704.html [6]FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078707.html [7]FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078708.html [8]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078703.html [9]FAILED winbot / zope.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078709.html [10] FAILED winbot / zope.exceptions_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078711.html [11] FAILED winbot / zope.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078706.html [12] FAILED winbot / zope.viewlet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078705.html ___ 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: 4, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-10 00:00:00 UTC and 2013-09-11 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]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078685.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078686.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078684.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078687.html ___ 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: 4, OK: 8
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote: On 09/09/2013 11:53 AM, Marius Gedminas wrote: On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest? IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support, built on top of WebTest, waiting in the py3 branch for... Actually, I'm not sure what it is waiting for. (I thought ZODB with Python 3 support, but it doesn't look like zope.testbrowser depends on ZODB, at least not directly.) Andrey? 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: 4, OK: 8
On Tue, Sep 10, 2013 at 09:32:18AM +0300, Marius Gedminas wrote:
On Mon, Sep 09, 2013 at 12:26:33PM -0400, Tres Seaver wrote:
On 09/09/2013 11:53 AM, Marius Gedminas wrote:
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote:
On 09/07/2013 07:00 PM, Zope tests summarizer wrote:
[1]FAILED winbot / zope.app.authentication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html
[2]FAILED winbot / zope.app.http_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html
[3]FAILED winbot / zope.app.publication_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html
[4]FAILED winbot / zope.app.wsgi_py_265_32
https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html
All four show the same failure in the bulidout phase:
% ---
While: Installing test. Error: There is a version conflict. We
already have: webtest 2.0.7
% ---
Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few
days ago, and it has install_requires = ['WebTest = 1.3.4'].
OTOH it wasn't me who added that = constraint, that happened a year
ago:
https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91
I just made a release with all the accumulated changes.
Looks like that was Adam: maybe we should be trying to push out a
version of z.tb compatible with current WebTest?
IIRC there's a brand new zope.testbrowser 4.1.0 with Python 3 support,
built on top of WebTest, waiting in the py3 branch for... Actually, I'm
not sure what it is waiting for. (I thought ZODB with Python 3 support,
but it doesn't look like zope.testbrowser depends on ZODB, at least not
directly.)
Indeed, and it's had no changes for at least 5 months and been tested
with a few existing codebases.
+1 for releasing it
Andrey?
Marius Gedminas
--
http://pov.lt/ -- Zope 3/BlueBream consulting and development
___
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 )
--
Brian Sutherland
___
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: 4, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-09 00:00:00 UTC and 2013-09-10 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]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078669.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078670.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078668.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078671.html ___ 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: 1, OK: 8
On 09/09/2013 04:29 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/08/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html Same failure as yesterday:: Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 Odd that the other three cleared up (or didn't they run?) All 4 ran, all 4 failed. Maybe it's a timing issue between the bot and the mailer? -- Best regards, Adam GROSZER -- Quote of the day: To be sure of hitting the target, shoot first, and call whatever you hit the target. ___ 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: 4, OK: 8
On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. 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: 4, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/09/2013 11:53 AM, Marius Gedminas wrote: On Sat, Sep 07, 2013 at 08:27:04PM -0400, Tres Seaver wrote: On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 % --- Could be my fault. I released zope.testbrowser 4.0.3 to PyPI a few days ago, and it has install_requires = ['WebTest = 1.3.4']. OTOH it wasn't me who added that = constraint, that happened a year ago: https://github.com/zopefoundation/zope.testbrowser/commit/699a18bb2868d23cd7ab3da80cf394b75f977d91 I just made a release with all the accumulated changes. Looks like that was Adam: maybe we should be trying to push out a version of z.tb compatible with current WebTest? 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/ iEYEARECAAYFAlIt9rkACgkQ+gerLs4ltQ4G+ACeJA6XZdZzR0EXWWWuiHAGJNTY TPQAnAgR9Uj3L1IqT5a1+sLrDugHAF8c =vHtg -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: 2, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-08 00:00:00 UTC and 2013-09-09 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]winbot / zope.app.http_py_265_32 [2]winbot / zope.app.wsgi_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 winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078654.html [2]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078655.html ___ 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: 1, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-07 00:00:00 UTC and 2013-09-08 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]winbot / zope.app.wsgi_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 winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html ___ 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: 1, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/08/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078639.html Same failure as yesterday:: Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 Odd that the other three cleared up (or didn't they run?) 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/ iEYEARECAAYFAlItMpcACgkQ+gerLs4ltQ599gCffh0g1nBUURxpDXFFEoaupA2+ uPIAoLWsd3X8o4UR3tU3nXDo/J8xaAtB =1TqS -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: 4, OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-06 00:00:00 UTC and 2013-09-07 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]winbot / zope.app.authentication_py_265_32 [2]winbot / zope.app.http_py_265_32 [3]winbot / zope.app.publication_py_265_32 [4]winbot / zope.app.wsgi_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 winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html ___ 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: 4, OK: 8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/07/2013 07:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078621.html [2]FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078622.html [3]FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078620.html [4]FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-September/078623.html All four show the same failure in the bulidout phase: - % --- c:\buildslave\zope.app.wsgi\buildcall C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\VCVARSALL.bat x86 Setting environment for using Microsoft Visual Studio 2008 x86 tools. Develop: 'c:\\buildslave\\zope.app.wsgi\\build\\.' Installing test. While: Installing test. Error: There is a version conflict. We already have: webtest 2.0.7 - % --- 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/ iEYEARECAAYFAlIrxFgACgkQ+gerLs4ltQ4R+QCfTmElgT9bLTKi//6JtRWoZ17S +l8An2nWUfe7sGMijMkDqSAVIeMH5A6/ =E0GF -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 - OK: 8
This is the summary for test reports received on the zope-tests list between 2013-09-05 00:00:00 UTC and 2013-09-06 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 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 -- ___ 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: 9, OK: 11
On 09/05/2013 02:58 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. It looks like the distribute/setuptools hell broke in. Maybe Patrick changed something? -- Best regards, Adam GROSZER -- Quote of the day: Character is a strange blending of flinty strength and pliable warmth. - Robert Shaffer ___ 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: 9, OK: 11
On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote: On 09/05/2013 02:58 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. It looks like the distribute/setuptools hell broke in. Maybe Patrick changed something? I'm guessing an upgrade of /usr/local/bin/virtualenv-2.7 to some version that ignores --distribute (since it's superseded by setuptools). Unfortunately buildout's bootstrap.py really really *really* wants to have distribute. BTW the last build was successful, so Patrick figured out how to appease bootstrap.py in the end. 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: 9, OK: 11
I am messing with my chef setup. I didn't figure out how to do this on a test environment yet. Sorry for the noise. On Thu, Sep 5, 2013 at 9:29 AM, Marius Gedminas mar...@gedmin.as wrote: On Thu, Sep 05, 2013 at 08:53:54AM +0200, Adam GROSZER wrote: On 09/05/2013 02:58 AM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. It looks like the distribute/setuptools hell broke in. Maybe Patrick changed something? I'm guessing an upgrade of /usr/local/bin/virtualenv-2.7 to some version that ignores --distribute (since it's superseded by setuptools). Unfortunately buildout's bootstrap.py really really *really* wants to have distribute. BTW the last build was successful, so Patrick figured out how to appease bootstrap.py in the end. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development ___ 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 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: 9, OK: 11
This is the summary for test reports received on the zope-tests list between 2013-09-03 00:00:00 UTC and 2013-09-04 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]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Successful - zopetoolkit_trunk - Build # 377 Successful - zopetoolkit_trunk - Build # 390 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 Failure - zopetoolkit_trunk - Build # 379 https://mail.zope.org/pipermail/zope-tests/2013-September/078564.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 380 https://mail.zope.org/pipermail/zope-tests/2013-September/078565.html [3]FAILED Still Failing - zopetoolkit_trunk - Build # 381 https://mail.zope.org/pipermail/zope-tests/2013-September/078566.html [4]FAILED Still Failing - zopetoolkit_trunk - Build # 382 https://mail.zope.org/pipermail/zope-tests/2013-September/078567.html [5]FAILED Still Failing - zopetoolkit_trunk - Build # 383 https://mail.zope.org/pipermail/zope-tests/2013-September/078568.html [6]FAILED Still Failing - zopetoolkit_trunk - Build # 384 https://mail.zope.org/pipermail/zope-tests/2013-September/078569.html [7]FAILED Still Failing - zopetoolkit_trunk - Build # 385 https://mail.zope.org/pipermail/zope-tests/2013-September/078570.html [8]FAILED Still Failing - zopetoolkit_trunk - Build # 386 https://mail.zope.org/pipermail/zope-tests/2013-September/078571.html [9]FAILED Still Failing - zopetoolkit_trunk - Build # 387 https://mail.zope.org/pipermail/zope-tests/2013-September/078572.html ___ 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: 9, OK: 11
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/04/2013 07:00 PM, Zope tests summarizer wrote: [1]Failure - zopetoolkit_trunk - Build # 379 Fixed - zopetoolkit_trunk - Build # 389 [2]Still Failing - zopetoolkit_trunk - Build # 380 [3]Still Failing - zopetoolkit_trunk - Build # 381 [4]Still Failing - zopetoolkit_trunk - Build # 382 [5]Still Failing - zopetoolkit_trunk - Build # 383 [6]Still Failing - zopetoolkit_trunk - Build # 384 [7]Still Failing - zopetoolkit_trunk - Build # 385 [8]Still Failing - zopetoolkit_trunk - Build # 386 [9]Still Failing - zopetoolkit_trunk - Build # 387 Anybody understand what caused those errors? There isn't any activity during the range of time represented by those failures. 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/ iEYEARECAAYFAlIn1y4ACgkQ+gerLs4ltQ7wbgCfQm179NVXtzqG6reuHXLM09Us 3IYAnR8WFF9mFvoW/a5fS+Hq4VSbrZy8 =be6K -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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-02 00:00:00 UTC and 2013-09-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 Successful - zopetoolkit_trunk - Build # 376 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 -- ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-09-01 00:00:00 UTC and 2013-09-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 Successful - zopetoolkit_trunk - Build # 375 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 -- ___ 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 - OK: 9
This is the summary for test reports received on the zope-tests list between 2013-08-31 00:00:00 UTC and 2013-09-01 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 Successful - zopetoolkit_trunk - Build # 374 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 -- ___ 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 )
