[Zope-dev] Zope Tests: 4 OK, 2 Failed
Summary of messages to the zope-tests list. Period Wed Dec 3 12:00:00 2008 UTC to Thu Dec 4 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures - Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 3 20:26:53 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010590.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Wed Dec 3 20:28:23 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010591.html Tests passed OK --- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Dec 3 20:20:52 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010586.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 3 20:22:22 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010587.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 3 20:23:52 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010588.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Wed Dec 3 20:25:22 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-December/010589.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zope.app.publisher/trunk/ - Menu items registered with browser:page/ were not re-registered after the
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Zagrodnick wrote: Log message for revision 93600: - Menu items registered with browser:page/ were not re-registered after the first functional test layer ran. In any subsequent functional test layer the items where not availabe (introduced in 3.5.0a3). I removed the transient registry for menuitems registered with the page directives. Since no test fails without it and I have a test which fails with it I feel quite comfortable. If this code is still required add a test case and proper clean up code. Changed: U zope.app.publisher/trunk/CHANGES.txt A zope.app.publisher/trunk/src/zope/app/publisher/browser/tests/menutestlayer.zcml A zope.app.publisher/trunk/src/zope/app/publisher/browser/tests/test_menutestlayer.py U zope.app.publisher/trunk/src/zope/app/publisher/browser/viewmeta.py -=- Modified: zope.app.publisher/trunk/CHANGES.txt === --- zope.app.publisher/trunk/CHANGES.txt 2008-12-04 05:11:53 UTC (rev 93599) +++ zope.app.publisher/trunk/CHANGES.txt 2008-12-04 07:19:40 UTC (rev 93600) @@ -8,6 +8,10 @@ - Added possibility to specify custom item class in menuItem, subMenuItem and addMenuItem directives using the ``item_class`` argument (LP #291865). +- Menu items registered with browser:page/ were not re-registered after the + first functional test layer ran. In any subsequent functional test layer the + items where not availabe (introduced in 3.5.0a3). + 3.5.2a1 (2008-10-23) That CHANGES.txt is out of whack: there is no 3.5.2a1 tag in SVN (nor should there be: we don't do alphas for bugfix-only micro-releases). Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJN9kV+gerLs4ltQ4RAvKCAJ9KuilO6CBxKjlVfQPDYpX/hMio7QCfQ/Ns Vwefmd1DgxW1xjPHxDX31fk= =vklM -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: Zope Tests: 4 OK, 2 Failed]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: Tres Seaver wrote: Hanno Schlichting wrote: In general all tests pass now, when run from the eggified Zope in: svn://svn.zope.org/repos/main/Zope2.buildout/trunk I just vendor imported mechanize 0.1.9 into the Zope SVN, and have changed the svn:external in my Z2 trunk checkout to point to it. I then made a separate tree and vendor imported ClientForm 0.2.9, including hacking on the faked-out package we are using to support svn:externals, and switched the external to point to it. At this point, the 'aqlegacy_ftest' doctest still fails in my trunk sandbox, as does the 'zope.testborwser.README' doctest. Hhm, the zope.testbrowser tests aren't run in the buildout version. It doesn't run tests for egg dependencies. I tried this again and now that aqlegacy_ftest fails for me again as well. Either a test interdependency or a timing issue I'd guess. My hypothesis is that one or more of the 'svn:externals' changes Sidnei made to bring in 2.6-compatible packages is the culprit (maybe an interaction between several of them). I am attaching readable diff for each of 'lib/python', 'lib/python/zope', and 'lib/python/zope/app'. As an aside / vent: the reason for the now-removed EXTERNALS.txt files was to keep the canonical information about the externals in a diffable file: why subversion can't do a proper diff on its own line-oriented property is beyond me. Another benefit of an EXTERNALS.txt file was that it could be inspected in the web view of a directory, which isn't true for the svn:externals property itself. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJN/NL+gerLs4ltQ4RApouAJ0WUYuUh3btoXQaLNNBLISqXcVFJACgyhsB YP0uIear89z8b5qP2x6F6Gs= =slqV -END PGP SIGNATURE- 2,3c2,3 ClientForm svn://svn.zope.org/repos/main/Zope3/trunk/src/ClientForm RestrictedPython svn://svn.zope.org/repos/main/RestrictedPython/tags/3.4.2/src/RestrictedPython --- ClientForm svn://svn.zope.org/repos/main/ClientForm/as_package/0.2.9 RestrictedPython svn://svn.zope.org/repos/main/RestrictedPython/tags/3.4.3/src/RestrictedPython 6c6 ZEO svn://svn.zope.org/repos/main/ZODB/tags/3.8.1/src/ZEO --- ZEO svn://svn.zope.org/repos/main/ZODB/branches/3.8/src/ZEO 10c10 mechanizesvn://svn.zope.org/repos/main/Zope3/trunk/src/mechanize --- mechanizesvn://svn.zope.org/repos/main/mechanize/tags/0.1.9/mechanize 17,18d16 12c12 documenttemplate svn://svn.zope.org/repos/main/zope.documenttemplate/tags/3.4.0/src/zope/documenttemplate --- documenttemplate svn://svn.zope.org/repos/main/zope.documenttemplate/tags/3.4.2/src/zope/documenttemplate 32c32 rdb svn://svn.zope.org/repos/main/zope.rdb/tags/3.4.0/src/zope/rdb --- rdb svn://svn.zope.org/repos/main/zope.rdb/tags/3.4.2/src/zope/rdb 44,45c44,45 testbrowser svn://svn.zope.org/repos/main/zope.testbrowser/tags/3.4.2-zope2/src/zope/testbrowser testing svn://svn.zope.org/repos/main/zope.testing/tags/3.5.3/src/zope/testing --- testbrowser svn://svn.zope.org/repos/main/zope.testbrowser/tags/3.5.1/src/zope/testbrowser testing svn://svn.zope.org/repos/main/zope.testing/tags/3.5.6/src/zope/testing 51d50 4c4 appsetup svn://svn.zope.org/repos/main/zope.app.appsetup/tags/3.4.1/src/zope/app/appsetup --- appsetup svn://svn.zope.org/repos/main/zope.app.appsetup/tags/3.8.0/src/zope/app/appsetup 9,10c9,10 componentsvn://svn.zope.org/repos/main/zope.app.component/tags/3.4.1/src/zope/app/component containersvn://svn.zope.org/repos/main/zope.app.container/tags/3.5.3/src/zope/app/container --- componentsvn://svn.zope.org/repos/main/zope.app.component/tags/3.5.0/src/zope/app/component containersvn://svn.zope.org/repos/main/zope.app.container/tags/3.6.2/src/zope/app/container 18c18 form svn://svn.zope.org/repos/main/zope.app.form/tags/3.4.1/src/zope/app/form --- form svn://svn.zope.org/repos/main/zope.app.form/tags/3.6.3/src/zope/app/form 33,34c33,34 publication svn://svn.zope.org/repos/main/zope.app.publication/tags/3.4.3/src/zope/app/publication publishersvn://svn.zope.org/repos/main/zope.app.publisher/tags/3.4.1/src/zope/app/publisher --- publication svn://svn.zope.org/repos/main/zope.app.publication/tags/3.5.0/src/zope/app/publication publishersvn://svn.zope.org/repos/main/zope.app.publisher/tags/3.5.1/src/zope/app/publisher 38c38 security
Re: [Zope-dev] [Fwd: Zope Tests: 4 OK, 2 Failed]
Previously Tres Seaver wrote: As an aside / vent: the reason for the now-removed EXTERNALS.txt files was to keep the canonical information about the externals in a diffable file: why subversion can't do a proper diff on its own line-oriented property is beyond me. Another benefit of an EXTERNALS.txt file was that it could be inspected in the web view of a directory, which isn't true for the svn:externals property itself. If only svn.zope.org had a trac-based browser, which does show those properties properly... Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: Zope Tests: 4 OK, 2 Failed]
On Thu, Dec 04, 2008 at 04:21:51PM +0100, Wichert Akkerman wrote: Previously Tres Seaver wrote: As an aside / vent: the reason for the now-removed EXTERNALS.txt files was to keep the canonical information about the externals in a diffable file: why subversion can't do a proper diff on its own line-oriented property is beyond me. Another benefit of an EXTERNALS.txt file was that it could be inspected in the web view of a directory, which isn't true for the svn:externals property itself. If only svn.zope.org had a trac-based browser, which does show those properties properly... Like this one: http://zope3.pov.lt/trac/browser ? Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) -- Brian Sutherland ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: Zope Tests: 4 OK, 2 Failed]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sidnei da Silva wrote: Hi Tres, On Thu, Dec 4, 2008 at 1:12 PM, Tres Seaver [EMAIL PROTECTED] wrote: My hypothesis is that one or more of the 'svn:externals' changes Sidnei made to bring in 2.6-compatible packages is the culprit (maybe an interaction between several of them). I am attaching readable diff for each of 'lib/python', 'lib/python/zope', and 'lib/python/zope/app'. As an aside / vent: the reason for the now-removed EXTERNALS.txt files was to keep the canonical information about the externals in a diffable file: why subversion can't do a proper diff on its own line-oriented property is beyond me. Another benefit of an EXTERNALS.txt file was that it could be inspected in the web view of a directory, which isn't true for the svn:externals property itself. I agree with your analysis: it is certainly related to the changes in externals, but maybe not for the reason you think! Last I looked at this, I found out that the failing zope.testbrowser test did not exist in the previous version of zope.testbrowser that we were pulling as externals. So I think that means we are missing an upgrade to some external that makes zope.testbrowser tests work when run standalone. That's just my feeling though, and I don't have much right now to back this claim. (CC'ing the newsgroup). OK, so the buildout.cfg for zope.testbrowser 3.5.1 (the version now linked into the Zope trunk) has: [versions] mechanize = 0.1.9 setuptools = 0.6c9 zope.testbrowser = zope.publisher = 3.5.1 zope.app.publication = 3.4.2 The version of zope.app.publication linked into the Zope trunk is 3.5.0 (bumped from 3.4.3). However, zope.app.publication is not listed as any kind of dependency in either version's setup.py. In fact, it isn't imported (or referenced in ZCML) anywhere other than in the buildout.cfg :(. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJOAoY+gerLs4ltQ4RAnkMAJ49XjAka9QWdnuLLIQO6rbqk/fWFgCeMlZ9 cYqP4W6I28xMOKGfTW20WTk= =iitF -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: Zope Tests: 4 OK, 2 Failed]
Tres Seaver wrote: As an aside / vent: the reason for the now-removed EXTERNALS.txt files was to keep the canonical information about the externals in a diffable file: why subversion can't do a proper diff on its own line-oriented property is beyond me. Another benefit of an EXTERNALS.txt file was that it could be inspected in the web view of a directory, which isn't true for the svn:externals property itself. Tres. I want to support this. The noise made by keeping EXTERNALS.txt in svn is very low compared to the signal it provides. -- Godefroid Chapelle (aka __gotcha) http://bubblenet.be ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
