Re: [Zope-dev] zope-tests - FAILED: 14, OK: 15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/09/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. [3]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071249.html [4]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071250.html [5]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071251.html [6]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071252.html These failures are in tests of now-out-of-date BTrees. We should just remove such tests from the ZODB suite, now that BTrees have their own CI. [11] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071259.html [12] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071258.html [13] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071256.html [14] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071257.html These failures are due to an oddity in the ZCML-based class protections granted by zope.app.security to the (non-API) tree iterators in the C BTrees code. I assume from the fact that these tests fail, that they are running against a BTrees package which does *not* have the C extensions compiled. Those iterator classes are not APIs: they are implementation details of the BTrees C extensions. I speculate somebody added protections for them to zope.app.security to work around an issue with walking space-suit-wrapped BTrees in untrusted code (note that somehow the corresponding TreeSets aren't protected: go figure). I pushed a branch of BTrees which restores the iterators *in name only* in the pure-Python case: https://github.com/zopefoundation/BTrees/tree/expose_tree_iterator Im my branch, trying to actually *use* the XXTreeITerator class in that branch (assuming no C extensions) will raise an exception, but the ZCML class declarations which name the classes should no longer raise. 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/ iEYEARECAAYFAlDu9yAACgkQ+gerLs4ltQ6LGQCdFWY+ol5kZiF7j+MaQlpSo302 4UQAoKOt/TZqWxN9eGMkCZXRJKqx8rhv =8dk5 -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: 14, OK: 15
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 12:15 PM, Tres Seaver wrote: [1]FAILED Still Failing - zopetoolkit_trunk - Build # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html These failures are both due to failures to check out 'transaction', which is now moved to Github. I think I have just fixed these failures by updating the 'ztk-sources.cfg' file to point to the github locations.'bin/develop co '.*' workds, and all tests pass. 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/ iEYEARECAAYFAlDu/FgACgkQ+gerLs4ltQ5BXQCgmtqqTs/zmZTpGe14KOyFgdo4 i34AnA2/mvomHm0IlH2ZnaOLSWo3f8Sm =sPeY -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: 14, OK: 15
This is the summary for test reports received on the zope-tests list between 2013-01-08 00:00:00 UTC and 2013-01-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]Still Failing - zopetoolkit_trunk - Build # 135 [2]Still Failing - zopetoolkit_trunk_app - Build # 118 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 [3]winbot / ZODB_dev py_265_win32 [4]winbot / ZODB_dev py_265_win64 [5]winbot / ZODB_dev py_270_win32 [6]winbot / ZODB_dev py_270_win64 [7]winbot / z3c.baseregistry_py_265_32 [8]winbot / z3c.contents_py_265_32 [9]winbot / z3c.recipe.paster_py_265_32 [10] winbot / z3c.sampledata_py_265_32 [11] winbot / zope.app.container_py_265_32 [12] winbot / zope.app.exception_py_265_32 [13] winbot / zope.app.testing_py_265_32 [14] winbot / zope.app.zcmlfiles_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 # 135 https://mail.zope.org/pipermail/zope-tests/2013-January/071231.html [2]FAILED Still Failing - zopetoolkit_trunk_app - Build # 118 https://mail.zope.org/pipermail/zope-tests/2013-January/071232.html [3]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071249.html [4]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071250.html [5]FAILED winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2013-January/071251.html [6]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071252.html [7]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071240.html [8]FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071253.html [9]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071254.html [10] FAILED winbot / z3c.sampledata_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071255.html [11] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071259.html [12] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071258.html [13] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071256.html [14] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071257.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 )
