Re: [Zope-dev] zope-tests - FAILED: 22, OK: 12, UNKNOWN: 2
On Thu, Feb 28, 2013 at 01:00:02AM +, Zope tests summarizer wrote: > [1]Still Failing - zopetoolkit_trunk - Build # 186 Same six failures, caused by ImportError: No module named persistent inside BTrees. Weird. > [2]Still Failing - zopetoolkit_trunk_app - Build # 168 Email lag, I suppose; this job was supposed to be shut down. > [3]UNKNOWN : Zope-trunk Python-2.6.8 : Linux > [4]UNKNOWN : Zope-trunk Python-2.7.3 : Linux Something new: Zope-trunk Python-2.6.8 : Linux (x86_64) Running ./bin/alltests --all /home/stefan/autotest/zope_runtests_4.sh: line 13: ./bin/alltests: No such file or directory Zope moved to github, I guess. Somebody ping the owners of zope-te...@epy.co.at please. > [5]winbot / z3c.authenticator_py_265_32 > [6]winbot / z3c.breadcrumb_py_265_32 > [7]winbot / z3c.configurator_py_265_32 > [8]winbot / z3c.contents_py_265_32 Moved to github. > [9]winbot / z3c.form_py_265_32 > [10] winbot / z3c.formui_py_265_32 No lxml on winbot > [11] winbot / z3c.pagelet_py_265_32 > [12] winbot / z3c.sampledata_py_265_32 Moved to github. > [13] winbot / zc.resourcelibrary_py_265_32 Bootstrap failed with Downloading http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg While: Initializing. An internal error occurred due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\buildout.py", line 1865, in main command, args) File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\buildout.py", line 203, in __init__ data['buildout'].copy(), override, set())) File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\buildout.py", line 1510, in _open downloaded)) File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\buildout.py", line 1452, in _open path, is_temp = download(filename) File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\download.py", line 99, in __call__ local_path, is_temp = self.download(url, md5sum, path) File "c:\temp\tmpofxyvs\zc.buildout-1.7.1-py2.6.egg\zc\buildout\download.py", line 185, in download os.remove(tmp_path) WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-htl5_d' > [14] winbot / zope.app.pagetemplate_py_265_32 Same \r\n issues. > [15] winbot / zope.app.server_py_265_32 > [16] winbot / zope.app.server_py_265_32 Moved to github. > [17] winbot / zope.app.wsgi_py_265_32 Same PEP- thing. > [18] winbot / zope.browserpage_py_265_32 Same \r\n issues. > [19] winbot / zope.generations_py_265_32 Moved to github. > [20] winbot / ztk_10 py_254_win32 > [22] winbot / ztk_11 py_254_win32 An error occurred when trying to install coverage 3.5.3. Look above this message for any errors that were output by easy_install. error: Setup script exited with error: command 'gcc' failed: No such file or directory While: Installing test-ztk. Getting distribution for 'coverage==3.5.3'. Error: Couldn't install: coverage 3.5.3 > [21] winbot / ztk_10 py_265_win64 > [23] winbot / ztk_11 py_265_win64 > [24] winbot / ztk_11 py_270_win64 An error occurred when trying to install coverage 3.5.3. Look above this message for any errors that were output by easy_install. Traceback (most recent call last): ... File "c:\Python26_64\lib\distutils\msvc9compiler.py", line 284, in query_vcvarsall raise ValueError(str(list(result.keys( ValueError: [u'path'] While: Installing test-ztk. Getting distribution for 'coverage==3.5.3'. Error: Couldn't install: coverage 3.5.3 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: 22, OK: 12, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2013-02-26 00:00:00 UTC and 2013-02-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 [1]Still Failing - zopetoolkit_trunk - Build # 186 [2]Still Failing - zopetoolkit_trunk_app - Build # 168 [3]UNKNOWN : Zope-trunk Python-2.6.8 : Linux [4]UNKNOWN : Zope-trunk Python-2.7.3 : Linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [5]winbot / z3c.authenticator_py_265_32 [6]winbot / z3c.breadcrumb_py_265_32 [7]winbot / z3c.configurator_py_265_32 [8]winbot / z3c.contents_py_265_32 [9]winbot / z3c.form_py_265_32 [10] winbot / z3c.formui_py_265_32 [11] winbot / z3c.pagelet_py_265_32 [12] winbot / z3c.sampledata_py_265_32 [13] winbot / zc.resourcelibrary_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.server_py_265_32 [16] winbot / zope.app.server_py_265_32 [17] winbot / zope.app.wsgi_py_265_32 [18] winbot / zope.browserpage_py_265_32 [19] winbot / zope.generations_py_265_32 [20] winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 [21] winbot / ztk_10 py_265_win64 [22] winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [23] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [24] winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 186 https://mail.zope.org/pipermail/zope-tests/2013-February/072879.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 168 https://mail.zope.org/pipermail/zope-tests/2013-February/072878.html [3]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.8 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072885.html [4]UNKNOWN UNKNOWN : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072886.html [5]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072901.html [6]FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072899.html [7]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072905.html [8]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072902.html [9]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072908.html [10] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072877.html [11] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072904.html [12] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072907.html [13] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072906.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072875.html [15] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072909.html [16] FAILED winbot / zope.app.server_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072874.html [17] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072900.html [18] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072903.html [19] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072876.html [20] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072887.html [21] FAILED winbot / ztk_10 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072889.html [22] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072890.html [23] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072892.html [24] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072894.html __
Re: [Zope-dev] ZTK 2.0 process
On Wed, Feb 27, 2013 at 5:04 PM, Sebastien Douche wrote: > 2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout > 2. Both do now. You currently need z3c.recipe.compattest from trunk though. I updated the ZTK trunk in the last days, and most of it should work under Python 3.3 now. To test do: svn co svn://svn.zope.org/repos/main/zopetoolkit/trunk ztk-trunk cd ztk-trunk python3.3 bootstrap.py bin/buildout bin/test-ztk Locally I get test failures for 10 packages - since not all are ported yet. But the overall buildout and test infrastructure works. Note that this is pulling in ZODB, ZEO and the compattest recipe from Git/SVN via mr.developers auto-checkout option. For everything else it uses (alpha) releases. If you want to test the master of every package, you have to run "bin/buildout -c development.cfg". > Can you tell me what is missing or deprecated in this list ? > https://github.com/sdouche/zopetoolkit-py3.3/blob/master/ztk.cfg Best check back against the canonical file in SVN as mentioned above. 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 )
Re: [Zope-dev] ZTK 2.0 process
On Wed, Feb 27, 2013 at 11:04:46AM -0500, Sebastien Douche wrote: > 2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout > 2. The latter has been fixed in zc.recipe.testrunner 2.0.0. 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] ZTK 2.0 process
On Tue, Feb 26, 2013 at 12:12 PM, Stephan Richter
wrote:
> Is anyone here willing to start a buildbot using Python 3.3 to test the ZTK?
I created a buildbot (the 1.1 branch) two months ago[1]:
http://buildbot.afpy.org/ztk1.1dev/builders/Python3.3.0%20Linux%2064bit
Ready to launch a new one with ZTK 1.2 / 2.0 / whatever. In the same
time, i test regularly the Zope3 packages in my own way[2] (testing
with mr.developer is cool but I want to test "official" packages on
the PyPI) . A bit hard 'cause:
1. Some essential packages are broken (ZODB, zope.app.wsgi,
zope.index). It's a pain to "simulate" the missing packages.
2. z3c.recipe.compattest and zc.recipe.testrunner doesn't work with Buildout 2.
>> - Add support for Python 3.x (either 3.3 or 3.2 and 3.3)
>
> Since I was unwilling to change all u'...' to u('...'), most packages
> currently only have Python 3.3 support. By the time ZTK 2.0 will be released,
> I think most people will have switched to Python 3.3.
+1
>> - Drop all zope.app packages from the KGS (most were deprecated in ZTK 1.1)
>
> Some of the zope.app packages (the ones not deprecated) should stay or simply
> be renamed to not being called zope.app.*.
All? In my mind, some zope.app are essentials like zope.app.wsgi,
zope.app.appsetup or zope.app.testing.
> We will also need to add a few packages, such as BTrees, persistent,
> transaction, etc. and deprecate/remove some others like zope.broken,
> zope.untrustedpython, zope.fixers, and zope.apidoc.
Can you tell me what is missing or deprecated in this list ?
https://github.com/sdouche/zopetoolkit-py3.3/blob/master/ztk.cfg
[1] https://mail.zope.org/pipermail/zope-dev/2012-December/044964.html
[2] https://github.com/sdouche/zopetoolkit-py3.3
--
Sebastien Douche
Twitter: @sdouche / G+: +sdouche
___
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] ZTK 2.0 process
Hi, On 2/26/13 7:26 PM, Hanno Schlichting wrote: snip > Our rule for inclusion in the ZTK is: Whatever library is used by at > least two out of the three frameworks (BlueBream, Grok, Zope). > > Given that BlueBream hasn't seen any release beyond a 1.0 about two > years back, I'm not sure it's active or relevant anymore. Grok isn't > seeing frequent releases, but there was a 1.5.5 mid last year. > > If you compare the version list from the last ZTK 1.1.5 > (http://download.zope.org/zopetoolkit/index/1.1.5/zopeapp-versions.cfg) > and Grok 1.5.5 (http://grok.zope.org/releaseinfo/1.5.5/versions.cfg), > you'll notice that Grok already overwrites the version requirement for > half of the non-deprecated packages with its own versions. And as I > said, Zope isn't using any of them anymore for a long time. > > So I don't see any value in testing and promising stability for those > zope.app packages, when there aren't any shared consumers for the > specific versions. > > And the actually used versions by Grok are: > zope.app.applicationcontrol, zope.app.appsetup, zope.app.debug - > renaming those to a non zope.app prefix doesn't make a lot of sense > for me either - as they are all about a specific app server > configuration and not generally reusable libraries. Agreed, from a Grok perspective: if there is no shared interested anymore in the zope.app.* packages, Grok will need to take up maintainership for those itself. In a way we already did by upping the versions of several of those package already. The zope.app.* packages that really are in use for a vanilla Grok-based application are zope.app.applicationcontrol, zope.app.appsetup and zope.app.debug and zope.app.wsgi. If there would be a strong drive from the Grok community to have Python 3 compatibility, they (and that includes me :) ) should port those zope.app.* packages or build the equivalents. I'll make note of this on the Grok dev list as well. 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] ZTK 2.0 process
Hi, On 2/26/13 5:04 PM, Hanno Schlichting wrote: > Hi. > > The process for a ZTK 2.0 release isn't really well defined. I'm not > sure if Jan-Wijbrand and Christophe are still interested in working on > ZTK releases. I'm personally and from a business-perspective still interested in the ZTK and to have Grok to be a relevant (to the ZTK process) "consumer" of the ZTK. That said, I've been off of the radar for a while concerning the ZTK because: 1) busy and 2) Grok's proven to be fairly stable and thus did not need much maintenance for quite a while. So: * Thanks Stephan and Hanno to get this ball rolling again * Thanks to whoever ported so many of the ZTK packages to Python 3 already! * I'll need to blow of some dust from my ZTK-knowledge and how Grok is using it to give you useful input to your questions. 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] ZTK 2.0 process
On Tue, Feb 26, 2013 at 4:45 PM, Stephan Richter wrote: > Hi everyone, > > We are about 5-6 packages away from porting ZTK to Python 3 That's awesome! //Lennart ___ 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: 21, OK: 15, UNKNOWN: 1
On Wed, Feb 27, 2013 at 11:52:56AM +0100, Patrick Gerken wrote: > Both the daily zope app tests and the zope app tests that run with each > commits have been deactivated. > > And Marius, thanks for dedication to look into the errors each day! I tricked myself into looking at this task as a way to play with my new toy https://gist.github.com/mgedmin/4995950 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: 21, OK: 15, UNKNOWN: 1
Hi, Both the daily zope app tests and the zope app tests that run with each commits have been deactivated. And Marius, thanks for dedication to look into the errors each day! Best regards, Patrick On Wed, Feb 27, 2013 at 8:21 AM, Marius Gedminas wrote: > On Wed, Feb 27, 2013 at 08:55:21AM +0200, Marius Gedminas wrote: > > > [3]Still Failing - zopetoolkit_trunk_app - Build # 167 > > > > Build #168: > > > > /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found > > Given http://zope3.pov.lt/trac/changeset/129871/zopetoolkit (aka "remove > all traces of zopeapp including test-zopeapp") this job should be disabled. > > > > [5]winbot / z3c.contents_py_265_32 > > > [12] winbot / zope.app.authentication_py_265_32 > > > [13] winbot / zope.app.authentication_py_265_32 > > > [18] winbot / zope.ptresource_py_265_32 > > > [19] winbot / zope.ptresource_py_265_32 > > > > Moved to github. > > These are already corrected in SVN. > > 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 )
