[Zope-dev] zope-tests - FAILED: 4, OK: 36, UNKNOWN: 2
This is the summary for test reports received on the zope-tests list between 2011-08-09 00:00:00 UTC and 2011-08-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 Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux [1]FAILED (errors=1) : Zope-2.13-alltests Python-2.6.6 : Linux [2]UNKNOWN : winbot / ZODB_dev py_270_win32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit [3]ZTK 1.0dev / Python2.4.6 Linux 64bit [4]ZTK 1.0dev / Python2.5.5 Linux 64bit [5]ZTK 1.0dev / Python2.6.5 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-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.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win64 [6]winbot / zope.app.interface_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_dev py_254_win32 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN FAILED (errors=1) : Zope-2.13-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-August/047981.html [2]UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/047961.html [3]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/047969.html [4]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/047971.html [5]FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/047970.html [6]FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-August/047973.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] More information in case of ZCML conflict errors
Le 02/08/11 15:29, Sylvain Viollon a écrit : > > Hello, > > I spend a long time trying to understand why I could not override a > component in ZCML and debug the error. > > First, includeOverrides doesn't include any overriding registration. > At least not like you would expect. At best It can be used to include a > package > in the site.zcml that would conflict with an another, replacing the > conflicting actions > by his own. > > After I would love, when there is a conflict error in ZCML to have a bit > more > of information other than what we currently have: like which file include > which file > and so up to the conflicting actions. As I pdb through this conflict, I > see that > all this information is already there, it is just not included in the > exception nor > displayed to the user. > > This information can be found in zope.configuration.config line 1517, in > the variable includepath and basepath. This just need to be added to the > exception. > > Since I work with Zope and ZCML, having those informations to debug > conflict errors would have saved me days of works, at least. > > My issue was that an another package was already including the package > that contained > actions I wanted to override, so even if I wanted to include it myself in > order to > override its actions, it would not be included since it already have been > included. > > Finally, I think a bit of documentation on ZCML conflict errors would > help a lot > everybody. > > Regards, > > Sylvain, > I bumped recently on the exact same issue. I totally agree with your statements. I think it is really worth changing the message issued by the configuration conflict errors. I hope I will be able to work on this in the coming weeks. Sylvain, I'll let you know. -- Godefroid Chapelle (aka __gotcha) http://bubblenet.be ___ 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 )
