Re: [Zope-dev] zope-tests - FAILED: 21, OK: 19
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: On Tue, Feb 26, 2013 at 01:00:02AM +, Zope tests summarizer wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' ... [11] winbot / z3c.layer.ready2go_py_265_32 [12] winbot / z3c.layer.ready2go_py_265_32 ZopeXMLConfigurationError: File c:\buildslave\z3c.layer.ready2go\build\src\z3c\layer\ready2go\ftesting.zcml, line 62.2-62.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' Okay, this does cause a test failure. Scratch that, a layer setup failure. Broken z3c.form release that's missing some locales? Some packages have special build steps (compile *.mo or something) before you're supposed to do setup.py sdist register upload. I've released z3c.form 3.0.0a2 with the missing locale files. Looks like it was a simple case of an incomplete MANIFEST.in [13] winbot / z3c.recipe.paster_py_265_32 Error: Couldn't find a distribution for 'beautifulsoup4'. Fixed. Marius three fixes before breakfast 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: 19
On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' and then we have the form id name vs form name id in README.txt that I cannot reproduce. Figured out why: I need to bin/buildout -n buildout:prefer-final=true and then I can reproduce this fine. [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 Same old Invalid request id returned. Because request ID is None in the response, and there's an error message in the JSON about 'TypeError: expecting a bytes object, got unicode'. This error is caused by zope.publisher 4.0.0a1: bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes the test pass, while bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes them fail. 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: 19
On Tue, Feb 26, 2013 at 02:41:02PM +0200, Marius Gedminas wrote: On Tue, Feb 26, 2013 at 08:54:01AM +0200, Marius Gedminas wrote: [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.contents_py_265_32 There's this lovely bit at the beginning I don't remember from before, but it's not counted as a test failure: ZopeXMLConfigurationError: File c:\buildslave\z3c.contents\build\src\z3c\contents\ftesting.zcml, line 41.2-41.32 ZopeXMLConfigurationError: File c:\eggs\z3c.form-3.0.0a1-py2.6.egg\z3c\form\configure.zcml, line 37.2-37.51 WindowsError: [Error 3] The system cannot find the path specified: u'c:\\eggs\\z3c.form-3.0.0a1-py2.6.egg\\z3c\\form\\locales\\*.*' and then we have the form id name vs form name id in README.txt that I cannot reproduce. Figured out why: I need to bin/buildout -n buildout:prefer-final=true and then I can reproduce this fine. Fixed. [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 Same old Invalid request id returned. Because request ID is None in the response, and there's an error message in the JSON about 'TypeError: expecting a bytes object, got unicode'. This error is caused by zope.publisher 4.0.0a1: bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes the test pass, while bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes them fail. Not fixed: going to lunch. (also, I need to review the changes in zope.publisher to see why it started complaining _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] ZTK 2.0 process
Hi everyone, what is the process to start working on ZTK 2.0? We are about 5-6 packages away from porting ZTK to Python 3 and I would like to start working on a new release. 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 )
Re: [Zope-dev] zope-tests - FAILED: 21, OK: 19
On Tuesday, February 26, 2013 02:41:02 PM Marius Gedminas wrote: This error is caused by zope.publisher 4.0.0a1: bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc makes the test pass, while bin/buildout -n buildout:prefer-final=false buildout:versions=versions \ versions:zope.publisher='4.0.0a1' \ versions:zope.session='4.0.0a1' bin/test -pvc This brings up a bigger question: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). If it is okay with everyone, we could change the releases to their final version numbers with the understanding that Python 3 support will not be available until all dependencies have their final release. Python 2 should work just fine once we get the trunk builds back to green. 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 )
Re: [Zope-dev] ZTK 2.0 process
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. Contrary to wait I said before I'd be willing to work on a ZTK 2.0 release (knowing the tools and procedure). My goals for a 2.0 release would be (comparing to http://docs.zope.org/zopetoolkit/releases/overview-1.1.html): - Drop support for Python 2.5 (ZTK 1.1 still supports that) - Add support for Python 3.x (either 3.3 or 3.2 and 3.3) - Drop all zope.app packages from the KGS (most were deprecated in ZTK 1.1) - Update to buildout 2 - Update to ZODB 4 Hanno On Tue, Feb 26, 2013 at 4:45 PM, Stephan Richter stephan.rich...@gmail.com wrote: Hi everyone, what is the process to start working on ZTK 2.0? We are about 5-6 packages away from porting ZTK to Python 3 and I would like to start working on a new release. 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 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 Tuesday, February 26, 2013 05:04:26 PM Hanno Schlichting wrote:
Contrary to wait I said before I'd be willing to work on a ZTK 2.0
release (knowing the tools and procedure).
Could you outline what the first step would be to create an alpha release list
for 2.0? We could manually include an sdist of the ZODB 4 py3 branch to make
the tests pass under Python 3.
Is anyone here willing to start a buildbot using Python 3.3 to test the ZTK?
My goals for a 2.0 release would be (comparing to
http://docs.zope.org/zopetoolkit/releases/overview-1.1.html):
Great!
- Drop support for Python 2.5 (ZTK 1.1 still supports that)
Yeah, none of the 4.0 packages do.
- 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.
- 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.*.
- Update to buildout 2
Yep, already done for all 4.0 packages.
- Update to ZODB 4
This will be a requirement for Py3 support or is anyone willing to backport
all the changes to ZODB3? :-)
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.
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 )
Re: [Zope-dev] ZTK 2.0 process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2013 11:04 AM, Hanno Schlichting wrote: My goals for a 2.0 release would be (comparing to http://docs.zope.org/zopetoolkit/releases/overview-1.1.html): - Drop support for Python 2.5 (ZTK 1.1 still supports that) +1. - Add support for Python 3.x (either 3.3 or 3.2 and 3.3) I would prefer 3.2 and 3.3. The major hurdle for 3.2-compatibility is unicode literals: I volunteer to do the work if needed to fix that up for the 3.3-ported packages. - Drop all zope.app packages from the KGS (most were deprecated in ZTK 1.1) +sys.maxint - Update to buildout 2 - Update to ZODB 4 +1 to both. 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/ iEYEARECAAYFAlEs7IoACgkQ+gerLs4ltQ5zCACfbHYVhZES9b6BBnj/OKLytaNu MToAnAyA//okvxRZdWrDL5XxgTBA7GSQ =2JJu -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: 21, OK: 19
On Tue, Feb 26, 2013 at 08:48:10AM -0500, Stephan Richter wrote: This brings up a bigger question: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). If it is okay with everyone, we could change the releases to their final version numbers with the understanding that Python 3 support will not be available until all dependencies have their final release. Python 2 should work just fine once we get the trunk builds back to green. I'm not a fan of non-alpha versions of packages depending on alpha versions of other packages, so -0.5. 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: 19
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/26/2013 10:46 AM, Stephan Richter wrote: Even though, most ported packages are fully Python 3 compatible, they might depend on packages that are not ready to get a final release. Those two are: * zope.security 4.0.0 (pending PyPy support from Tres) To be clear: what is missing is the pure-Python reference implementation of the spacesuit proxies: without having that in place, passing the same tests as the C version, and at 100% statement coverage, I'm not convinced the Py3k port is correct (even though the C version passes all its existing tests under Py3k). Essentially, I rushed the Py3k port in order not to block others working on porting dependents. I have relevant experience in the zope.proxy port that doing the reference implementation actually uncovers bugs in the C implementation. * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) AFAIK, the remaining test failures on Py33 are largely spurious (doctest repr issues, or else are pending the fork to use 'zodbpickle'. Any package that depends directly or indirectly on those two packages has an alpha release right now. Strictly speaking this is not necessary for any package not depending on ZODB (ZODB is special because the dep changes from ZODB3 to ZODB). Packages which are still bleeding-edge themselves should be OK with pinning non-final releases of their dependencies. 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/ iEYEARECAAYFAlEs+EcACgkQ+gerLs4ltQ5AigCeLY5NgANp+RLFYyzpFUZa0hBM v58AoIy2utc2SMHK2ibjIgMvW5aW5CmP =9em0 -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] ZTK 2.0 process
On Tue, Feb 26, 2013 at 6:12 PM, Stephan Richter stephan.rich...@gmail.com wrote: Could you outline what the first step would be to create an alpha release list for 2.0? We could manually include an sdist of the ZODB 4 py3 branch to make the tests pass under Python 3. I'll have to look at the procedure again a bit. Will do so in the next days and start updating svn.zope.org/repos/main/zopetoolkit/trunk - 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.*. 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. 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] zope-tests - FAILED: 21, OK: 19
On Tuesday, February 26, 2013 01:00:39 PM Tres Seaver wrote: * ZODB 4.0.0 (I am currently using an sdist of the py3 branch.) AFAIK, the remaining test failures on Py33 are largely spurious (doctest repr issues, or else are pending the fork to use 'zodbpickle'. So the state here is: - We need to include zodbpickle in order to make pickle loading backward- compatible with Python 2. Without this you cannot take you Python 2 ZODB and open it in Python 3. (zodbpickle's docs provide details.) - Make noload() work in zodbpickle. I ported the code from cPickle, but it does not work. This prohibits GC without the ability to load the objects. noload() also needs a Python implementation and tests. I only know that noload() is not working because of a failure in the ZODB tests. - Python 2 and 3 pickles have different sizes due to some added padding and some other reasons Marius has reported. Using zodbpickle will not fix that, since it is a fork of _pickle.c from Python 3.3. We simply should fix the tests to live with that fact. That's pretty much it. 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: 21, OK: 15, UNKNOWN: 1
This is the summary for test reports received on the zope-tests list between 2013-02-25 00:00:00 UTC and 2013-02-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 [1]FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux [2]Still Failing - zopetoolkit_trunk - Build # 185 [3]Still Failing - zopetoolkit_trunk_app - Build # 167 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [4]winbot / z3c.authenticator_py_265_32 [5]winbot / z3c.contents_py_265_32 [6]winbot / z3c.form_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 [9]winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsontree_py_265_32 [11] winbot / zc.resourcelibrary_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.wsgi_py_265_32 [16] winbot / zope.browserpage_py_265_32 [17] winbot / zope.generations_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 [20] winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 [21] winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 [22] winbot / ztk_11 py_270_win64 Non-OK results -- [1]UNKNOWN FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux https://mail.zope.org/pipermail/zope-tests/2013-February/072853.html [2]FAILED Still Failing - zopetoolkit_trunk - Build # 185 https://mail.zope.org/pipermail/zope-tests/2013-February/072845.html [3]FAILED Still Failing - zopetoolkit_trunk_app - Build # 167 https://mail.zope.org/pipermail/zope-tests/2013-February/072846.html [4]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072868.html [5]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072866.html [6]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072872.html [7]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072839.html [8]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072843.html [9]FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072838.html [10] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072840.html [11] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072870.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072871.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072837.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072841.html [15] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072867.html [16] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072869.html [17] FAILED winbot / zope.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072844.html [18] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072873.html [19] FAILED winbot / zope.ptresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072842.html [20] FAILED winbot / ztk_11 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-February/072857.html [21] FAILED winbot / ztk_11 py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072859.html [22] FAILED winbot / ztk_11 py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-February/072861.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
Re: [Zope-dev] zope-tests - FAILED: 21, OK: 15, UNKNOWN: 1
On Wed, Feb 27, 2013 at 01:00:01AM +, Zope tests summarizer wrote: [1]FAILED (failures=1) : Zope-trunk Python-2.7.3 : Linux Failure in test test_combined_scored_search_planned (Products.ZCatalog.tests.test_catalog.TestScoring) Traceback (most recent call last): File /home/stefan/autotest/temp/python27-zope214all/eggs/Products.ZCatalog-3.0-py2.7.egg/Products/ZCatalog/tests/test_catalog.py, line 1099, in test_combined_scored_search_planned self.assertEqual(brains[0].title, '111') AssertionError: '11' != '111' [2]Still Failing - zopetoolkit_trunk - Build # 185 Build #186 has failures in - test-ztk-zope.traversing - test-ztk-zope.dublincore - test-ztk-zope.container - test-ztk-zope.component - test-ztk-zope.catalog - test-ztk-zope.ramcache All of them are variations of ImportError: No module named persistent which is sort of surprising, given Getting required 'persistent' required by ZODB 4.0.0dev. We have a develop egg: persistent 4.0.7dev [3]Still Failing - zopetoolkit_trunk_app - Build # 167 Build #168: /tmp/hudson2996479762744665535.sh: 1: ./bin/test-zopeapp: not found and I just noticed, early on there's + ./bin/develop up -f /tmp/hudson2610355406837563482.sh: 1: ./bin/develop: not found [4]winbot / z3c.authenticator_py_265_32 Same Unicode prefix thing. [5]winbot / z3c.contents_py_265_32 Moved to github. [6]winbot / z3c.form_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 Same: failure to build lxml. [9]winbot / z3c.jsonrpc_py_265_32 svn step failed with exceptions.WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\buildslave\\z3c.jsonrpc\\build' [10] winbot / z3c.jsontree_py_265_32 Last build is successful! [11] winbot / zc.resourcelibrary_py_265_32 buildout step failed with WindowsError: [Error 32] The process cannot access the file because it is being used by another process: 'c:\\temp\\buildout-eex7yk' [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.authentication_py_265_32 Moved to github [14] winbot / zope.app.pagetemplate_py_265_32 Same \r\n differences. [15] winbot / zope.app.wsgi_py_265_32 Same PEP- violation. [16] winbot / zope.browserpage_py_265_32 Same \r\n differences. [17] winbot / zope.generations_py_265_32 [18] winbot / zope.ptresource_py_265_32 [19] winbot / zope.ptresource_py_265_32 Moved to github. [20] winbot / ztk_11 py_254_win32 [21] winbot / ztk_11 py_265_win64 [22] winbot / ztk_11 py_270_win64 Error: Couldn't install: coverage 3.5.3 (winbot compiler troubles that I'm not qualified to debug) 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
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 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
On Wednesday, February 27, 2013 08:55:21 AM Marius Gedminas wrote: [6]winbot / z3c.form_py_265_32 [7]winbot / z3c.form_py_265_32 [8]winbot / z3c.formui_py_265_32 Same: failure to build lxml. z3c.form used to pin lxml 2.3, which I did not even see on PyPI anymore. Unfortuantely the bot building Windows binaries is not running anymore. 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 )
