Re: [Zope-dev] zope-tests - FAILED: 45, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2013 05:16 AM, Marius Gedminas wrote: > Options: - add zope.untrustedpython to the ZTK - switch zope.security > to the 3.9 branch > > I'm leaning towards option 1, but I don't know the procedure for > adding something to the ZTK. Help? +1 for adding it. The ZTK is still managed in SVN: svn+ssh://svn.zope.org/repos/main/zopetoolkit/trunk You should be able to add it to the three config files used to build / test the ZTK: - ztk.cfg - ztk-sources.cfg - ztk-versions.cfg > Incidentally, the changelog on the PyPI page for zope.security has no > mention of 3.9.x, but the branch (and a 3.9.0 tag) exists in SVN? > What happened there? Just an oversight. The history goes something like: - - I released zope.proxy 4.1.0, breaking BBB for then-current zope.security 3.8.3. which had been made from the trunk (2012-12-19). - - I then made the 3.8 branch, and released 3.8.4, pinning z.proxy < 4.1dev (2012-12-21). - - Discovering that 3.8.4 included the trunk version of the proxy.h header, I made the 3.8.5 release, copying in the compatible header (2012-12-20). - - FBO the ZTK trunk, I made the 3.9 release, pinning z.proxy >= 4.1.0, and including the compatilbe proxy.h header. We just need to fold in that history, which is present on the 3.8 and 3.9 branches, but not the trunk. I will check that in now. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEf3esACgkQ+gerLs4ltQ4r4wCdEWKUe0uv3CZKJJZs1H7IU/qC 3bwAn2Eu9Kgh563OxegUPmESoRo8wYJ6 =kcnq -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: 45, OK: 20
On Sat, Feb 16, 2013 at 01:00:02AM +, Zope tests summarizer wrote: > [1]FAILED Still Failing - zopetoolkit_trunk - Build # 174 >https://mail.zope.org/pipermail/zope-tests/2013-February/072375.html Build # 175 is more interesting: Error: Picked: zope.untrustedpython = 4.0.0 Options: - add zope.untrustedpython to the ZTK - switch zope.security to the 3.9 branch I'm leaning towards option 1, but I don't know the procedure for adding something to the ZTK. Help? Incidentally, the changelog on the PyPI page for zope.security has no mention of 3.9.x, but the branch (and a 3.9.0 tag) exists in SVN? What happened there? > [3]FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux >https://mail.zope.org/pipermail/zope-tests/2013-February/072374.html Looked at this briefly, didn't have time to debug to completion. > [4]FAILED winbot / z3c.authenticator_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2013-February/072397.html Interesting test failure: Test-module import failures: Module: z3c.authenticator.tests Traceback (most recent call last): File "c:\buildslave\z3c.authenticator\build\src\z3c\authenticator\tests.py", line 19, in from z3c.authenticator import testing File "c:\buildslave\z3c.authenticator\build\src\z3c\authenticator\testing.py", line 22, in from zope.app.testing import setup File "c:\eggs\zope.app.testing-3.10.0-py2.6.egg\zope\app\testing\setup.py", line 59, in from zope.app.testing.placelesssetup import setUp as placelessSetUp File "c:\eggs\zope.app.testing-3.10.0-py2.6.egg\zope\app\testing\placelesssetup.py", line 21, in from zope.i18n.testing import PlacelessSetup as I18nPlacelessSetup ImportError: cannot import name PlacelessSetup I guess zope.i18n 4.0.0a3, released yesterday, broke BBB. I've skipped most of the other failures because with a broken zope.app.testing I expect them all to be related. (I looked at zope.contentprovider randomly and saw it was the old error still, already fixed in the next build.) > [45] FAILED winbot / zope.security_py_265_32 >https://mail.zope.org/pipermail/zope-tests/2013-February/072367.html This is interesting: Failure in test test___repr___checker_forbids_str (zope.security.tests.test_proxy.ProxyCTests) Traceback (most recent call last): File "c:\Python26_32\lib\unittest.py", line 279, in run testMethod() File "c:\buildslave\zope.security\build\src\zope\security\tests\test_proxy.py", line 178, in test___repr___checker_forbids_str 'instance at 0x%0x>' % (_BUILTINS, id(target))) File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '' != '' Failure in test test___str___checker_forbids_str (zope.security.tests.test_proxy.ProxyCTests) Traceback (most recent call last): File "c:\Python26_32\lib\unittest.py", line 279, in run testMethod() File "c:\buildslave\zope.security\build\src\zope\security\tests\test_proxy.py", line 162, in test___str___checker_forbids_str 'instance at 0x%0x>' % (_BUILTINS, id(target))) File "c:\Python26_32\lib\unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '' != '' The number of leading zeroes in the hex representation of object addresses differs. 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: 45, OK: 20
This is the summary for test reports received on the zope-tests list between 2013-02-14 00:00:00 UTC and 2013-02-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 [1]Still Failing - zopetoolkit_trunk - Build # 174 [2]Still Failing - zopetoolkit_trunk_app - Build # 156 [3]Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [4]winbot / z3c.authenticator_py_265_32 [5]winbot / z3c.baseregistry_py_265_32 [6]winbot / z3c.breadcrumb_py_265_32 [7]winbot / z3c.configurator_py_265_32 [8]winbot / z3c.configurator_py_265_32 [9]winbot / z3c.contents_py_265_32 [10] winbot / z3c.jsonrpc_py_265_32 [11] winbot / z3c.jsonrpc_py_265_32 [12] winbot / z3c.language.switch_py_265_32 [13] winbot / z3c.layer.pagelet_py_265_32 [14] winbot / z3c.layer.ready2go_py_265_32 [15] winbot / z3c.menu.ready2go_py_265_32 [16] winbot / z3c.menu.ready2go_py_265_32 [17] winbot / z3c.pagelet_py_265_32 [18] winbot / z3c.password_py_265_32 [19] winbot / z3c.password_py_265_32 [20] winbot / z3c.pdftemplate_py_265_32 [21] winbot / z3c.ptcompat_py_265_32 [22] winbot / z3c.sampledata_py_265_32 [23] winbot / z3c.tabular_py_265_32 [24] winbot / z3c.template_py_265_32 [25] winbot / zc.sourcefactory_py_265_32 [26] winbot / zc.sourcefactory_py_265_32 [27] winbot / zope.app.applicationcontrol_py_265_32 [28] winbot / zope.app.applicationcontrol_py_265_32 [29] winbot / zope.app.form_py_265_32 [30] winbot / zope.app.generations_py_265_32 [31] winbot / zope.app.generations_py_265_32 [32] winbot / zope.app.pagetemplate_py_265_32 [33] winbot / zope.app.publication_py_265_32 [34] winbot / zope.app.rotterdam_py_265_32 [35] winbot / zope.app.rotterdam_py_265_32 [36] winbot / zope.app.schema_py_265_32 [37] winbot / zope.app.security_py_265_32 [38] winbot / zope.app.server_py_265_32 [39] winbot / zope.app.zcmlfiles_py_265_32 [40] winbot / zope.app.zopeappgenerations_py_265_32 [41] winbot / zope.contentprovider_py_265_32 [42] winbot / zope.formlib_py_265_32 [43] winbot / zope.formlib_py_265_32 [44] winbot / zope.pagetemplate_py_265_32 [45] winbot / zope.security_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 Non-OK results -- [1]FAILED Still Failing - zopetoolkit_trunk - Build # 174 https://mail.zope.org/pipermail/zope-tests/2013-February/072375.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 156 https://mail.zope.org/pipermail/zope-tests/2013-February/072376.html [3]FAILED Zope 3.4 Known Good Set / py2.4-64bit-linux https://mail.zope.org/pipermail/zope-tests/2013-February/072374.html [4]FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072397.html [5]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072406.html [6]FAILED winbot / z3c.breadcrumb_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072410.html [7]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072403.html [8]FAILED winbot / z3c.configurator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072370.html [9]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072402.html [10] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072398.html [11] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072355.html [12] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072412.html [13] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072372.html [14] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-February/072401.html [15]
