Re: [Zope-dev] Zope Tests: 71 OK, 16 Failed
Hello, I also suggest dropping the test reports for the z3c.* packages: they have been broken since the day they were added, AFAICT, which is a strong signal that they are not being maintained. The point of the daily reports is to *keep the board green*, so that when a new failure shows up, we *feel* motivated to fix it. Cluttering the report with repeated-and-apparently-never-gonna-fix failures is demotivating, which is the opposite of the effect we intend. They were *definitely* green before lxml 2.3 got released. I think Marius worked on getting them green. I don't think those problems are repeated-and-apparently-never-gonna-fix, because it's a matter of having lxml eggs/exe for all windows/python platforms. That is going to be a *blocker* for ZTK too sooner or later, because allmost all windows users are *not* able to compile. The fix right now seems to be to push Sidnei to do the releases. -- Best regards, Adam GROSZER -- Quote of the day: Do not make friends who are comfortable to be with. Make friends who will force you to lever yourself up. - Thomas J. Watson, Sr. ___ 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: 71 OK, 16 Failed
Hello, On Mon, 28 Feb 2011 14:08:29 -0500 you wrote: On Monday, February 28, 2011, Tres Seaver wrote: I also suggest dropping the test reports for the z3c.* packages: they have been broken since the day they were added, AFAICT, which is a strong signal that they are not being maintained. The problem is merely that lxml cannot be installed. This is more a winbot setup problem than a package one. And the reason lxml cannot be built is because libxml is missing. This is really strange, since there are binaries available for lxml-2.3 for Python 2.6. http://pypi.python.org/pypi/lxml/2.3 Does anyone with Windows Foo have any idea? Those seem to be 32bit only, weird is that only 32bit bots fail. Let it have one more day to clear up, maybe those eggs got released just after the bots ran. OTOH, I definitely do *not* want to enable winbot to be able to compile lxml. -- Best regards, Adam GROSZER -- Quote of the day: Fall seven times, stand up eight. - Japanese Proverb ___ 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: 71 OK, 16 Failed
On Tue, Mar 1, 2011 at 10:27 AM, Adam GROSZER agroszer...@gmail.com wrote: Hello, On Mon, 28 Feb 2011 14:08:29 -0500 you wrote: On Monday, February 28, 2011, Tres Seaver wrote: I also suggest dropping the test reports for the z3c.* packages: they have been broken since the day they were added, AFAICT, which is a strong signal that they are not being maintained. The problem is merely that lxml cannot be installed. This is more a winbot setup problem than a package one. And the reason lxml cannot be built is because libxml is missing. This is really strange, since there are binaries available for lxml-2.3 for Python 2.6. http://pypi.python.org/pypi/lxml/2.3 Does anyone with Windows Foo have any idea? Those seem to be 32bit only, weird is that only 32bit bots fail. Let it have one more day to clear up, maybe those eggs got released just after the bots ran. OTOH, I definitely do *not* want to enable winbot to be able to compile lxml. -- Best regards, Adam GROSZER -- Quote of the day: Fall seven times, stand up eight. - Japanese Proverb ___ 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 ) The build of z3c.* packages on winbot could be tested like http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 buildhttp://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 Regards Simon Elbaz ___ 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: 71 OK, 16 Failed
Hello, On Tue, 1 Mar 2011 11:04:30 +0100 you wrote: The build of z3c.* packages on winbot could be tested like http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 build http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 hm, that does not seem to have lxml as dependency -- Best regards, Adam GROSZER -- Quote of the day: Defeat may serve as well as victory to shake the soul and let the glory out. - Edwin Markham ___ 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: 71 OK, 16 Failed
On Tue, Mar 1, 2011 at 11:42 AM, Adam GROSZER agroszer...@gmail.com wrote: Hello, On Tue, 1 Mar 2011 11:04:30 +0100 you wrote: The build of z3c.* packages on winbot could be tested like http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 build http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 hm, that does not seem to have lxml as dependency -- Best regards, Adam GROSZER -- Quote of the day: Defeat may serve as well as victory to shake the soul and let the glory out. - Edwin Markham ___ 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 ) Hello, Sorry, I didn't expressed myself well. I mean building the test with the same steps as in http://dev.thehealthagency.com/buildbot/builders/zope2.13_win-py2.6%20slave-win/builds/161 : - svn update - svn info - python.exe bootstrap.py - bin\buildout.exe - bin\test.exe Regards Simon ___ 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: 83 OK, 14 Failed
Summary of messages to the zope-tests list. Period Mon Feb 28 12:00:00 2011 UTC to Tue Mar 1 12:00:00 2011 UTC. There were 97 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 27 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 47 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Mon Feb 28 11:26:25 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033417.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Mon Feb 28 16:04:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033445.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Mon Feb 28 22:13:20 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033468.html Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Mon Feb 28 22:13:54 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033469.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Mon Feb 28 22:14:01 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033470.html Subject: FAILED : winbot / z3c.form_py_265_32 From: buildbot at winbot.zope.org Date: Mon Feb 28 22:25:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033471.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Mon Feb 28 22:53:57 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033472.html Subject: FAILED : winbot / z3c.template_py_265_32 From: buildbot at winbot.zope.org Date: Mon Feb 28 23:02:59 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033473.html Subject: FAILED : winbot / zope.testrunner_py_265_32 From: buildbot at winbot.zope.org Date: Tue Mar 1 00:25:59 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033476.html Subject: FAILED : winbot / z3c.ptcompat_py_265_32 From: buildbot at winbot.zope.org Date: Tue Mar 1 00:30:25 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033477.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Tue Mar 1 00:35:43 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033478.html Subject: FAILED : winbot / z3c.macro_py_265_32 From: buildbot at winbot.zope.org Date: Tue Mar 1 00:36:49 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033479.html Subject: FAILED : winbot / z3c.pagelet_py_265_32 From: buildbot at winbot.zope.org Date: Tue Mar 1 00:41:20 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033480.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Tue Mar 1 03:39:16 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033490.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 09:49:35 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033395.html Subject: OK : Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 09:51:10 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033396.html Subject: OK : Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 09:52:35 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033397.html Subject: OK : Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 09:54:00 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033398.html Subject: OK : Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 09:55:29 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033399.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 10:01:28 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033400.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 10:07:15 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033401.html Subject: OK : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 10:13:03 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033402.html Subject: OK : Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 28 10:18:04 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033403.html Subject: OK : Zope Buildbot /
Re: [Zope-dev] Zope Tests: 83 OK, 14 Failed
Hello, Subject: FAILED : winbot / z3c.form_py_265_32 From: buildbot at winbot.zope.org Date: Mon Feb 28 22:25:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033471.html Now it seems like Malthe is the one to blaim... Good to have those bots, or not ;-) -- Best regards, Adam GROSZER -- Quote of the day: The wise shepherd never trusts his flock to a smiling wolf. ___ 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] Acquisition wrapped objects do not behave well on unicode call
On 2011-02-28 07:43:55 +0100, Christian Zagrodnick said: On 2011-02-25 21:56:49 +0100, David Glick said: On 2/20/11 1:32 AM, Christian Zagrodnick wrote: On 2011-02-19 17:17:44 +0100, Hanno Schlichting said: On Thu, Feb 17, 2011 at 8:27 AM, Christian Zagrodnickc...@gocept.com wrote: On 2011-02-16 22:22:53 +0100, Hanno Schlichting said: svn+ssh://svn.zope.org/repos/main/Acquisition/branches/zagy-unicode-should-be-called Sure. I'll review, merge and release. Should be sometime this week, cannot promise a day. Branch reviewed, merged and released in Acquisition 2.13.6. Could you remove the merged branch once you updated your buildout config? Done. Thanks for releasing! This change introduces a regression when calling unicode on wrapped objects that implement __str__ but not __unicode__. Essentially it is now doing the equivalent of str(aq_base(obj)) ... __str__ used to get a wrapped object as 'self', but now it is unwrapped. Here's a failing test that can be added to Acquisition's TestUnicode test case to demonstrate the issue: def test_str_fallback_is_still_wrapped(self): class A(Acquisition.Implicit): def __str__(self): return str(len(Acquisition.aq_chain(self))) wrapped = A().__of__(A()) self.assertEqual(u'2', unicode(wrapped)) This is currently causing some regressions in Plone tests. I'll have a look at it. Thanks for spotting that. Fixed in r120651 (trunk) - Fixed bug: When an object did not implement ``__unicode__``, calling ``unicode(wrapped)`` was calling ``__str__`` with an unwrapped ``self``. Is the situation with Plone better now? -- Christian Zagrodnick · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 4 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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] Acquisition wrapped objects do not behave well on unicode call
On 3/1/11 11:57 AM, Christian Zagrodnick wrote: This change introduces a regression when calling unicode on wrapped objects that implement __str__ but not __unicode__. Essentially it is now doing the equivalent of str(aq_base(obj)) ... __str__ used to get a wrapped object as 'self', but now it is unwrapped. Here's a failing test that can be added to Acquisition's TestUnicode test case to demonstrate the issue: def test_str_fallback_is_still_wrapped(self): class A(Acquisition.Implicit): def __str__(self): return str(len(Acquisition.aq_chain(self))) wrapped = A().__of__(A()) self.assertEqual(u'2', unicode(wrapped)) This is currently causing some regressions in Plone tests. I'll have a look at it. Thanks for spotting that. Fixed in r120651 (trunk) - Fixed bug: When an object did not implement ``__unicode__``, calling ``unicode(wrapped)`` was calling ``__str__`` with an unwrapped ``self``. Is the situation with Plone better now? Yes, this fixes the test failures we were seeing before. Thanks! David -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org Online tools and strategies for the environmental movement. Sign up for Groundwire News! http://groundwire.org/email-capture ___ 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 )
