August 2011 - Zope-Dev

zope-tests - FAILED: 10, OK: 29, UNKNOWN: 2
by Zope tests summarizer 20 Aug '11

20 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-18 00:00:00 UTC and 2011-08-19 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 [3] ZTK 1.0 / Python2.6.5 Linux 64bit [4] ZTK 1.0dev / Python2.4.6 Linux 64bit [5] ZTK 1.0dev / Python2.5.5 Linux 64bit [6] 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 [7] winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win64 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 [8] winbot / ztk_dev py_254_win32 [9] winbot / ztk_dev py_265_win32 [10] winbot / ztk_dev py_265_win64 [11] winbot / ztk_dev py_270_win32 [12] 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/048356.html [2] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048337.html [3] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048375.html [4] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048345.html [5] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048347.html [6] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048346.html [7] FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048373.html [8] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048359.html [9] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048360.html [10] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048361.html [11] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048362.html [12] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048363.html

1 0

disabling zope.schema constraint check in edit form
by Joshua Immanuel 19 Aug '11

19 Aug '11

Hello all, I use the zope.schema field's constraint parameter to check for the uniqueness of a particular field like this class IMyObject(Interface): def check_for_uniqueness(value): cat = getUtility(ICatalog) results = cat.searchResults(object_name=value) for rslt in results: if rslt.name.lower() == value.lower(): raise NameAlreadyExists(value) return True name = TextLine(title=u'Name', required=True, constraint=check_for_uniqueness) ... This goes well with the zope.formlib's AddForm. But in edit form if I modify any other field other than the 'name' field I get the 'NameAlreadyExists' error. Worse case scenario is where I have a cancel action button which just redirects to another page, that too screams for the NameAlreadyExists error. Is there a way to disable the constraint check in the EditForm if the 'name' field isn't modified? What is the preferred way of doing these kind of checks? Please guide me. -- Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in

4 6

zope.interface versions, ZTK 1.0 and later
by Tres Seaver 18 Aug '11

18 Aug '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been wrestling with Launchpad bugs for zope.interface lately, and would like to hear from folks about the issues involved. - ------------------------------------ %< -------------------------------- Overview - --------- - - Version 3.6.1 was the original ZTK 1.0 version. The substantial changes since then have been mostly due to issues which showed up while working on Python3 compatibility: o LP # 675064: Specify return value type for C optimizations module init under Python 3 (fixed in zope.interface 3.6.2). o LP 804951: InterfaceClass instances were unhashable under Python 3.x. (fixed in zope.interface 3.6.4). The fix here actually provoked the following bugs / fixes: o LP #811792: work around buggy behavior in some subclasses of 'zope.interface.interface.InterfaceClass', which invoke '__hash__' before initializing '__module__' and '__name__'. o Fix Python 2.5 incompatibility introduced in new tests of '__hash__'. o LP #825249: Fix test failure (only under 'python setup.py test') in those same new tests. At this point, the tests for the trunk (but not the main module itself) are not Python 2.4 compatible, because they try to test that a UserWarning is emitted using a 'with' statement. - - This fix is for non-CPython platforms: o LP #804832: Do not build C extension under PyPy or Jython. - - There is one issue not directly related to porting: o LP #570942: Now correctly compare interfaces from different modules but with the same names (fixed in 3.6.3). This fix is in two parts: it corrects extracting the '__module__' attribute, and adds the missing "rich comparison" operators ('__eq__', '__ne__', '__le__', '__ge__') The real "slippery slope" was adding '__eq__': it then required adding '__hash__', because Python's dictionary semantics require that objects which compare equal also hash equal, which then provokes the issues with subclasses which stash the instances in a dict before initializing the '__module__' and '__name__' attributes. - - The ZTK 1.0 branch was bumped to include zope.interface 3.6.3, which contained a number of the higer-risk changes, mostly made for porting purposes. Proposal - -------- - - Revert ZTK 1.0 to use zope.interface 3.6.1. (We can skip this part if the next step goes quickly). - - Create a 3.6 branch in SVN, and revert all the post-3.6.1 changes on it. Release a new 3.6.6 from this branch, possibly after applying a new, more minimal fix for LP #570942. - - Bump ZTK 1.0 to use the zope.interface 3.6.6. - - Freeze development on the 3.6 branch. - - Release a 3.7.0 version from the trunk, with all the porting changes intact. Update ZTK 1.1 to use 3.7.0, - ------------------------------------ %< -------------------------------- Thoughts? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5FdRAACgkQ+gerLs4ltQ5dnACfRSDauatZn1iMmefLsIQABcDJ nSgAoNyJu8AS3M9ndEWveo/pbIVEfSRU =gSl/ -----END PGP SIGNATURE-----

4 6

Re: [Zope-dev] SVN: zope.interface/trunk/ Fix a regression introduced in 3.6.4, that made one zope.app.interface test fail
by Tres Seaver 18 Aug '11

18 Aug '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/04/2011 10:18 AM, Gediminas Paulauskas wrote: > Log message for revision 122462: Fix a regression introduced in > 3.6.4, that made one zope.app.interface test fail > > > Changed: U zope.interface/trunk/CHANGES.txt U > zope.interface/trunk/src/zope/interface/interface.py > > -=- Modified: zope.interface/trunk/CHANGES.txt > =================================================================== > --- zope.interface/trunk/CHANGES.txt 2011-08-04 13:44:20 UTC (rev > 122461) +++ zope.interface/trunk/CHANGES.txt 2011-08-04 14:18:37 UTC > (rev 122462) @@ -11,10 +11,12 @@ > > - Fix testing deprecation warnings issued when tested under Py3K. > > +- Fix ``InterfaceClass.__hash__`` to match comparison function. + > 3.6.4 (2011-07-04) ------------------ > > -- LP 804951: InterfaceClass instances were unhashable under Python > 3.x. +- LP #804951: InterfaceClass instances were unhashable under > Python 3.x. > > 3.6.3 (2011-05-26) ------------------ > > Modified: zope.interface/trunk/src/zope/interface/interface.py > =================================================================== > --- zope.interface/trunk/src/zope/interface/interface.py 2011-08-04 > 13:44:20 UTC (rev 122461) +++ > zope.interface/trunk/src/zope/interface/interface.py 2011-08-04 > 14:18:37 UTC (rev 122462) @@ -682,7 +682,8 @@ return (n1 > n2) - (n1 > < n2) > > def __hash__(self): - return hash((self.__name__, > self.__module__)) + return hash((getattr(self, '__name__', > ''), + getattr(self, '__module__', ''))) I don't think this is a regression -- how do you legitimately create an interface without both those attributes? The point of the comparison function is to work even when handed a non-Interface object as one of the two terms being compared, which doesn't apply to the case of a hash. If there is code in zope.app.interface which is constructing a class derived from Interface but which doesn't call Interface.__init__ before hashing the instance, that code is *broken*, and should be fixed. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk48WjQACgkQ+gerLs4ltQ7ceACcCIkqWBXaISkGj44RIFTPqdyx d5kAn1H9biD8xF5T2Jf6kN/FQNBLRkbb =aTGc -----END PGP SIGNATURE-----

2 2

zope-tests - FAILED: 9, OK: 30, UNKNOWN: 2
by Zope tests summarizer 18 Aug '11

18 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-16 00:00:00 UTC and 2011-08-17 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 [3] ZTK 1.0 / Python2.6.5 Linux 64bit [4] ZTK 1.0dev / Python2.4.6 Linux 64bit [5] ZTK 1.0dev / Python2.5.5 Linux 64bit [6] 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 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 [7] winbot / ztk_dev py_254_win32 [8] winbot / ztk_dev py_265_win32 [9] winbot / ztk_dev py_265_win64 [10] winbot / ztk_dev py_270_win32 [11] 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/048274.html [2] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048255.html [3] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048293.html [4] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048263.html [5] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048265.html [6] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048264.html [7] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048277.html [8] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048278.html [9] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048279.html [10] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048280.html [11] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048281.html

1 0

zope-tests - FAILED: 9, OK: 30, UNKNOWN: 2
by Zope tests summarizer 17 Aug '11

17 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-15 00:00:00 UTC and 2011-08-16 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 [3] ZTK 1.0 / Python2.6.5 Linux 64bit [4] ZTK 1.0dev / Python2.4.6 Linux 64bit [5] ZTK 1.0dev / Python2.5.5 Linux 64bit [6] 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 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 [7] winbot / ztk_dev py_254_win32 [8] winbot / ztk_dev py_265_win32 [9] winbot / ztk_dev py_265_win64 [10] winbot / ztk_dev py_270_win32 [11] 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/048233.html [2] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048214.html [3] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048252.html [4] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048222.html [5] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048224.html [6] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048223.html [7] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048236.html [8] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048237.html [9] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048238.html [10] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048239.html [11] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048240.html

1 0

zope-tests - FAILED: 9, OK: 30, UNKNOWN: 2
by Zope tests summarizer 16 Aug '11

16 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-14 00:00:00 UTC and 2011-08-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 ---------------- 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 [3] ZTK 1.0 / Python2.6.5 Linux 64bit [4] ZTK 1.0dev / Python2.4.6 Linux 64bit [5] ZTK 1.0dev / Python2.5.5 Linux 64bit [6] 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 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 [7] winbot / ztk_dev py_254_win32 [8] winbot / ztk_dev py_265_win32 [9] winbot / ztk_dev py_265_win64 [10] winbot / ztk_dev py_270_win32 [11] 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/048192.html [2] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048173.html [3] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048211.html [4] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048181.html [5] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048183.html [6] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048182.html [7] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048195.html [8] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048196.html [9] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048197.html [10] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048198.html [11] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048199.html

1 0

Segfault in Acquisition in Zope 2
by Sylvain Viollon 15 Aug '11

15 Aug '11

Hello, I have a problem in my application that Zope segfault. I spend lot of time trying to narrowing the issue. To identify the problem quickly, I compiled Python in debug mode (to get all the assert and so on). As well I have my own WSGI publisher. I could not trigger the problem with ZServer (probably there are locks that prevent the problem to appear with ZServer, but I could not find them). As well, I forced a garbage collection at the end of each Zope requests. The problem occurs in garbage collection, and is identified by an assertion with Python in debug mode: Assertion failed: (gc->gc.gc_refs != 0), function update_refs, file Modules/gcmodule.c, line 311. (The comment in Python above that assert explains the bug that is happening). With this Python, I can reproduce using my application the problem just by displaying any ZMI screen (it assert/segfault right away if the browser cache is empty). The issue only happens in ZMI, and is triggered by the ZMI resources, stored using OFS.misc_. Resources in misc_ are set as attributes on a class (so they are module level variable, shared among all application threads), that is itself set as an attribute on the root Application. If, after the configuration of Zope, I monkey patch the misc_ and p_ attributes on the root Application, the ZMI obviously looks ugly but doesn't segfault, and works in a stable fashion. If I restrict my application to one thread only (without the monkey patch above) the ZMI works and doesn't segfault. 2 or more threads trigger the problem almost right away. I changed my content type icons in my application to be exported to the user using browser resources (provided by the Five product). That works and is stable. But I cannot change all the Zope built-in resources to do the same, instead of using that misc_ hack (which will be nicer I think anyway). If I let the application segfault (without the assert), I have a null pointer issues in an ImplicitAcquisitionWrapper that already have its content freed, and looks like it want to free it again. This looks like a race condition bug when accessing those resources exported using misc_. I tried, unsuccessfully up until now to write a small script that could reproduced the problem without all my application stack. I have this problem with: - Python 2.6 and Zope 2.12 - Python 2.7 and Zope 2.13 (All the latest ones). This have been observed on 64 bits computers (Mac OS X, FreeBSD and Linux). I don't know about 32 bits installations. Do you have any clues for me ? Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands

2 2

zope-tests - FAILED: 11, OK: 33, UNKNOWN: 2
by Zope tests summarizer 15 Aug '11

15 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-13 00:00:00 UTC and 2011-08-14 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] Repository policy check found errors in 300 projects [3] Total languishing bugs for zope2: 1 [4] Total languishing bugs for zope: 60 [5] Total languishing bugs for zopeapp: 2 [6] Total languishing bugs for zopetoolkit: 201 [7] UNKNOWN : winbot / ZODB_dev py_270_win32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [8] ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit 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 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 [9] winbot / ztk_dev py_254_win32 [10] winbot / ztk_dev py_265_win32 [11] winbot / ztk_dev py_265_win64 [12] winbot / ztk_dev py_270_win32 [13] 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/048151.html [2] FAILED Repository policy check found errors in 300 projects https://mail.zope.org/pipermail/zope-tests/2011-August/048133.html [3] FAILED Total languishing bugs for zope2: 1 https://mail.zope.org/pipermail/zope-tests/2011-August/048131.html [4] FAILED Total languishing bugs for zope: 60 https://mail.zope.org/pipermail/zope-tests/2011-August/048130.html [5] FAILED Total languishing bugs for zopeapp: 2 https://mail.zope.org/pipermail/zope-tests/2011-August/048126.html [6] FAILED Total languishing bugs for zopetoolkit: 201 https://mail.zope.org/pipermail/zope-tests/2011-August/048129.html [7] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048128.html [8] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048170.html [9] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048154.html [10] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048155.html [11] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048156.html [12] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048157.html [13] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-August/048158.html

1 0

zope-tests - FAILED: 2, OK: 36, UNKNOWN: 3
by Zope tests summarizer 14 Aug '11

14 Aug '11

This is the summary for test reports received on the zope-tests list between 2011-08-12 00:00:00 UTC and 2011-08-13 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] FAILED (failures=1) : Zope-trunk-alltests Python-2.6.6 : Linux [3] UNKNOWN : winbot / ZODB_dev py_270_win32 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [4] ZTK 1.0 / Python2.6.5 Linux 64bit [5] ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit 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 winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win64 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/048105.html [2] UNKNOWN FAILED (failures=1) : Zope-trunk-alltests Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-August/048107.html [3] UNKNOWN UNKNOWN : winbot / ZODB_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-August/048086.html [4] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048124.html [5] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-August/048094.html

2 1