Re: [Zope-dev] Zope Tests: 19 OK, 23 Failed, 3 Unknown
On Thu, Oct 07, 2010 at 01:58:31PM +0200, Zope Tests Summarizer wrote: > Summary of messages to the zope-tests list. > Period Wed Oct 6 12:00:00 2010 UTC to Thu Oct 7 12:00:00 2010 UTC. > There were 45 messages: 6 from Zope Tests, 8 from buildbot at pov.lt, 20 from > buildbot at winbot.zope.org, 11 from ccomb at free.fr. > > > Test failures > - > Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux > From: buildbot at pov.lt > Date: Wed Oct 6 21:03:25 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021194.html > > Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux > From: buildbot at pov.lt > Date: Wed Oct 6 21:46:30 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021197.html > > Subject: FAILED : Zope 3.4 Known Good Set / py2.5-64bit-linux > From: buildbot at pov.lt > Date: Wed Oct 6 22:03:27 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021200.html > > Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux > From: buildbot at pov.lt > Date: Wed Oct 6 23:07:46 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021202.html All four were caused by temporary network problems (virtualenv couldn't download setuptools/distribute). Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital 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: 42 OK, 8 Failed
On 10/07/2010 03:01 PM, Marius Gedminas wrote: > On Thu, Oct 07, 2010 at 08:52:41AM +0200, Jens Vagelpohl wrote: >> On 10/6/10 18:33 , Tres Seaver wrote: >>> +1 for dropping the test: if we aren't going to try to fix it to pass, >>> then scrap it. Note that I actually feel the same way about *all* the >>> every-day failures: the value of the every-day mail drops sharply when >>> there are any "expected" failures. >> >> For me personally the value has dropped so far that I am mostly ignoring >> those emails. > > I used to ignore them, now I pay attention. > >> They are hard to parse to begin with and there are just >> too many buildbot entries. > > What do you think about the overview table at > http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds > ? > >> I wonder if it would make sense to send >> separate emails per software package (such as ZTK, Zope2, etc) so that >> people can pick and choose. > > -1 for separate emails. One per day is plenty enough. > > +1 for better organization within the email. > > Currently the build results are grouped by status, and then ordered by > time. I'd prefer if they were grouped by status, and then grouped by OS > (or by project; don't care much) inside the larger per-status groups. I think that ordering by name, only showing the "bad" status is a better idea for the *summary*. Having a stable sorting makes it easier to look for "your" entry. Dropping the OKs will make noise go away. I also suggest a single URL in the mail to go to a more detailed page in case you care for something specific to avoid the noise of visible text urls sprinkled all over the place. Like this: /= SNIP Subject: Zope Tests: 42 OK, 8 Failed zc_buildout_dev py_244_win32 / winbot.zope.org - FAILED zope2.12 slave-osx / thehealthagency.com - FAILED zope2.12 slave-ubuntu64 / thehealthagency.com - UNKONWN ztk_dev py_254_win32 / winbot.zope.org - FAILED ztk_dev py_265_win32 / winbot.zope.org - FAILED ztk_dev py_265_win64 / winbot.zope.org - FAILED ztk_dev py_270_win32 / winbot.zope.org - FAILED ztk_dev py_270_win64 / winbot.zope.org - UNKNOWN Status details can be found here: http://example.com/zopetests/2010-01-12-00:30:15.html \= SNAP -- Christian Theune · c...@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · 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] Fun with vocabularies
Am 07.10.2010, 14:58 Uhr, schrieb Fred Drake : > Interestingly, I can't find anything that suggests "consolidation" by > searching that page for "mail" or "list". Was that what > "IRC/mailinglist rationalisation" means? Yes, that's the one. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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: 42 OK, 8 Failed
On Thu, Oct 07, 2010 at 08:52:41AM +0200, Jens Vagelpohl wrote: > On 10/6/10 18:33 , Tres Seaver wrote: > > +1 for dropping the test: if we aren't going to try to fix it to pass, > > then scrap it. Note that I actually feel the same way about *all* the > > every-day failures: the value of the every-day mail drops sharply when > > there are any "expected" failures. > > For me personally the value has dropped so far that I am mostly ignoring > those emails. I used to ignore them, now I pay attention. > They are hard to parse to begin with and there are just > too many buildbot entries. What do you think about the overview table at http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds ? > I wonder if it would make sense to send > separate emails per software package (such as ZTK, Zope2, etc) so that > people can pick and choose. -1 for separate emails. One per day is plenty enough. +1 for better organization within the email. Currently the build results are grouped by status, and then ordered by time. I'd prefer if they were grouped by status, and then grouped by OS (or by project; don't care much) inside the larger per-status groups. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital 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] Fun with vocabularies
On Thu, Oct 7, 2010 at 8:45 AM, Charlie Clark wrote: > This was the suggestion at the summit: > http://wiki.zope.org/ztk/ZopeSummit2010Summary Interestingly, I can't find anything that suggests "consolidation" by searching that page for "mail" or "list". Was that what "IRC/mailinglist rationalisation" means? -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ 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] Fun with vocabularies
Am 07.10.2010, 14:34 Uhr, schrieb Fred Drake : > Have you tried using a callable that provides > zope.schema.interfaces.IContextSourceBinder? > Looking at the code in 3.7.0 (the newest zope.schema in my egg cache), > that should work out of the box. Thanks for the tip. For a vocabulary it has to provide IBaseVocabulary as well, although I guess I can just define a source. Unfortunately I'm getting now getting an AssertionError when the widgets are setup but I now know where to look. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] Fun with vocabularies
Am 07.10.2010, 14:38 Uhr, schrieb Fred Drake : > Another consolidation? We already tossed the zope3-dev list. This was the suggestion at the summit: http://wiki.zope.org/ztk/ZopeSummit2010Summary Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] z3c.recipe.compattest buildout 1.5/1.4 compatibility
On 10/7/10 10:20 AM, Wolfgang Schnerring wrote: > * Jan-Wijbrand Kolman [2010-10-06 13:39]: >> BTW, I discussed updating the z3c.recipe.i18n for similar reasons - to >> support newer buildout features - in a separate thread. There people >> seemed to be +1 on releasing a recipe that declares its minimal buildout >> version requirement to be>= 1.5.1. Would you say that that situation is >> similar to this? > > Yes, I agree, that makes sense, so +1 from me here. Released as 0.13. Thanks for the feedback. regards, jw ___ 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] Fun with vocabularies
On Thu, Oct 7, 2010 at 8:35 AM, Charlie Clark wrote: > I thought we were consolidating the mailing lists? It is a developer's > rather than a user's question but I would agree not related to ZTK > development. Another consolidation? We already tossed the zope3-dev list. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ 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] Fun with vocabularies
Am 07.10.2010, 14:31 Uhr, schrieb Hanno Schlichting : > No offense, None taken. > but isn't this a question for a users mailing list? It's > not really about developing Zope itself, but developing with Zope > isn't it? I thought we were consolidating the mailing lists? It is a developer's rather than a user's question but I would agree not related to ZTK development. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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] Fun with vocabularies
On Thu, Oct 7, 2010 at 8:21 AM, Charlie Clark wrote: > I was wondering whether it's possible to use callables for schema > vocabularies without registering them first? ... > I'm sure it should be possible but my weak and feeble brain has somehow > failed to solve the puzzle! Have you tried using a callable that provides zope.schema.interfaces.IContextSourceBinder? Looking at the code in 3.7.0 (the newest zope.schema in my egg cache), that should work out of the box. -Fred -- Fred L. Drake, Jr. "A storm broke loose in my mind." --Albert Einstein ___ 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] z3c.recipe.i18n
On 10/6/10 10:27 AM, Jan-Wijbrand Kolman wrote: > On 10/6/10 9:53 AM, yuppie wrote: >> Jan-Wijbrand Kolman wrote: >>> This afternoon I merged the "gary-0.8.0" branch for z3c.recipe.i18n. The >>> recipe now uses and depends on zc.buildout-1.5.1 features. I'd like to >>> release this merge as 0.8.0 as this make it possible to move grok and >>> the groktoolkit over to zc.buildout-1.5.1. I guess this is also useful >>> in the light of moving the ZTK itself to zc.buildout 1.5.1 at some point. >>> >>> Unless there are objections of course :) >> >> +1 >> >> But could you please make it more explicit that 0.8.0 drops support for >> zc.buildout 1.4? Your CHANGES.txt note is not clear about that and maybe >> install_requires should specify the new requirement explicitly. > > Yes, agreed. Released as 0.80. regards, jw ___ 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] Fun with vocabularies
Hi. On Thu, Oct 7, 2010 at 2:21 PM, Charlie Clark wrote: > I was wondering whether it's possible to use callables for schema > vocabularies without registering them first? No offense, but isn't this a question for a users mailing list? It's not really about developing Zope itself, but developing with Zope isn't it? Hanno ___ 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] Fun with vocabularies
Hi, I was wondering whether it's possible to use callables for schema vocabularies without registering them first? ie. def my_vocab(context): while some_constraint: yield zope.schema.SimpleTerm() alsoProvides(my_vocab, zope.schema.interfacesIBaseVocabulary) class IMySchema(Interface): value = Choice( vocabulary=my_vocab ) I'm sure it should be possible but my weak and feeble brain has somehow failed to solve the puzzle! On a similar note: how should I handle i18n message objects that are the title of a SimpleTerm? At least in zope.formlib this leads to a rendering error because: "AttributeError: 'MessageFactory' object has no attribute 'replace'" Thanks for any pointers. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ 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: 19 OK, 23 Failed, 3 Unknown
Summary of messages to the zope-tests list. Period Wed Oct 6 12:00:00 2010 UTC to Thu Oct 7 12:00:00 2010 UTC. There were 45 messages: 6 from Zope Tests, 8 from buildbot at pov.lt, 20 from buildbot at winbot.zope.org, 11 from ccomb at free.fr. Test failures - Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 16:18:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021170.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 16:27:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021171.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Oct 6 16:36:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021172.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 16:45:00 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021173.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Oct 6 16:53:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021174.html Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 17:39:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021179.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 18:24:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021181.html Subject: FAILED : ZTK 1.0 / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Wed Oct 6 19:42:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021186.html Subject: FAILED : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Oct 6 20:55:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021190.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Oct 6 20:56:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021191.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Oct 6 20:57:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021192.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Wed Oct 6 21:01:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021193.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Wed Oct 6 21:03:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021194.html Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Wed Oct 6 21:21:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021195.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Wed Oct 6 21:21:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021196.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Wed Oct 6 21:46:30 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021197.html Subject: FAILED : Bluebream / Python2.5.5 64bit linux From: ccomb at free.fr Date: Wed Oct 6 22:01:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021199.html Subject: FAILED : Bluebream / Python2.4.6 64bit linux From: ccomb at free.fr Date: Wed Oct 6 22:01:25 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021198.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-64bit-linux From: buildbot at pov.lt Date: Wed Oct 6 22:03:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021200.html Subject: FAILED : Bluebream / Python2.6.5 64bit linux From: ccomb at free.fr Date: Wed Oct 6 22:04:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021201.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Wed Oct 6 23:07:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021202.html Subject: FAILED : Zope 3.4 KGS / Python2.4.6 64bit linux From: ccomb at free.fr Date: Thu Oct 7 00:03:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021203.html Subject: FAILED : Zope 3.4 KGS / Python2.5.5 64bit linux From: ccomb at free.fr Date: Thu Oct 7 00:04:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021204.html Unknown --- Subject: UNKNOWN : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Thu Oct 7 00:48:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021207.html Subject: UNKNOWN : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Oct 7 00:50:27 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests
Re: [Zope-dev] Zope Tests: 42 OK, 8 Failed
Hi! Patrick Gerken wrote: > On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman wrote: >> On 10/7/10 08:52 , Jens Vagelpohl wrote: >>> For me personally the value has dropped so far that I am mostly ignoring >>> those emails. They are hard to parse to begin with and there are just >>> too many buildbot entries. >> >> Likewise. I've redirected all test-mails to /dev/null for a long time. > > Which projects do you not want to see in this summary mail? I think we can distinguish two categories of tests: 1.) Tests that are expected to run without failures. If one of these tests fails, that's a regression that needs to be fixed immediately. 2.) Tests that frequently fail. These show issues that need to be resolved in the long run. I only want to see the first category in the summary mail. The second category just produces noise on the list and makes it hard to recognize failures in the first category. Cheers, Yuppie ___ 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: 42 OK, 8 Failed
On 10/7/10 11:35 , Patrick Gerken wrote: > On Thu, Oct 7, 2010 at 11:28, Wichert Akkerman wrote: >> On 10/7/10 11:26 , Hanno Schlichting wrote: >>> +1 for a brief summary, the direct links to the build results are >>> still important though and should be somewhere in the mail > > Please don't forget we also have a page that links to all buildbots > and display latest status too. > > http://docs.zope.org/zopetoolkit/process/buildbots.html That's certainly a hell of a lot better than those emails! It would be even nicer if there was a page with just the status information; as it is now I have to scroll two pages down to get to the useful data. Wichert. ___ 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: 42 OK, 8 Failed
On Thu, Oct 7, 2010 at 11:28, Wichert Akkerman wrote: > On 10/7/10 11:26 , Hanno Schlichting wrote: >> +1 for a brief summary, the direct links to the build results are >> still important though and should be somewhere in the mail Please don't forget we also have a page that links to all buildbots and display latest status too. http://docs.zope.org/zopetoolkit/process/buildbots.html Best regards, Patrick ___ 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: 42 OK, 8 Failed
On 10/7/10 11:26 , Hanno Schlichting wrote: > On Thu, Oct 7, 2010 at 11:22 AM, Wichert Akkerman wrote: >> Perhaps more important is brevity. If the mail was a simple thing with a >> maximum of 15 lines or so where you can immediately see if something is >> wrong or not it would be much better. Something like: >> >> PROBLEMS >> >> >> ZTK 1.0/python2.4: win32 5 errors, 2 failures >> GROK 1.1/python2.6: linux 2 errors > > +1 for a brief summary, the direct links to the build results are > still important though and should be somewhere in the mail Make it a multipart/alternative mail and use links in the html version so you can click on things without having to waste extra space on links? > >> and simply don't list things that do not have problems. > > I'd still list those at the bottom. We have a rather high variability > in the number of jobs run. I'd like to see if some jobs didn't run at > all and didn't sent any mails. That would be a problem that should be at the top. Wichert. ___ 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: 42 OK, 8 Failed
On Thu, Oct 7, 2010 at 11:22 AM, Wichert Akkerman wrote: > Perhaps more important is brevity. If the mail was a simple thing with a > maximum of 15 lines or so where you can immediately see if something is > wrong or not it would be much better. Something like: > > PROBLEMS > > > ZTK 1.0/python2.4: win32 5 errors, 2 failures > GROK 1.1/python2.6: linux 2 errors +1 for a brief summary, the direct links to the build results are still important though and should be somewhere in the mail > and simply don't list things that do not have problems. I'd still list those at the bottom. We have a rather high variability in the number of jobs run. I'd like to see if some jobs didn't run at all and didn't sent any mails. Hanno ___ 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: 42 OK, 8 Failed
On 10/7/10 11:09 , Patrick Gerken wrote: > On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman wrote: >> On 10/7/10 08:52 , Jens Vagelpohl wrote: >>> For me personally the value has dropped so far that I am mostly ignoring >>> those emails. They are hard to parse to begin with and there are just >>> too many buildbot entries. >> >> Likewise. I've redirected all test-mails to /dev/null for a long time. > > Which projects do you not want to see in this summary mail? Perhaps more important is brevity. If the mail was a simple thing with a maximum of 15 lines or so where you can immediately see if something is wrong or not it would be much better. Something like: PROBLEMS ZTK 1.0/python2.4: win32 5 errors, 2 failures GROK 1.1/python2.6: linux 2 errors and simply don't list things that do not have problems. Wichert. ___ 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: 42 OK, 8 Failed
On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman wrote: > On 10/7/10 08:52 , Jens Vagelpohl wrote: >> For me personally the value has dropped so far that I am mostly ignoring >> those emails. They are hard to parse to begin with and there are just >> too many buildbot entries. > > Likewise. I've redirected all test-mails to /dev/null for a long time. Which projects do you not want to see in this summary mail? Best regards, Patrick ___ 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: 42 OK, 8 Failed
On 10/7/10 08:52 , Jens Vagelpohl wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/6/10 18:33 , Tres Seaver wrote: >> +1 for dropping the test: if we aren't going to try to fix it to pass, >> then scrap it. Note that I actually feel the same way about *all* the >> every-day failures: the value of the every-day mail drops sharply when >> there are any "expected" failures. > > For me personally the value has dropped so far that I am mostly ignoring > those emails. They are hard to parse to begin with and there are just > too many buildbot entries. Likewise. I've redirected all test-mails to /dev/null for a long time. Wichert. ___ 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] z3c.recipe.compattest buildout 1.5/1.4 compatibility
* Jan-Wijbrand Kolman [2010-10-06 13:39]: > On 10/6/10 12:49 PM, Wolfgang Schnerring wrote: >> * Jan-Jaap Driessen [2010-10-05 18:09]: >>> Version 0.12.2 of z3c.recipe.compattest is not compatible with recent >>> versions of it's dependencies zc.buildout (v1.5.1), zc.recipe.egg >>> (v1.3.2) and z3c.recipe.scripts. I fixed this in revision 117253. >>> Is it OK with you to drop compatibility with zc.buildout versions< >>> 1.5 in the next release of z3c.recipe.compattest? >> >> I'm all for moving forward, but I don't really understand why the >> 1.5-update should cause such compatibility breakage. > > I think in this particular case z3c.recipe.compattest relied on > zc.buildout internals that now have have changed. So, no, I do not think > it really is an API change and as such it is not intentional breakage > nor something that __should__ be fixed in buildout. > > Ideally, z3c.recipe.compattest would be fixed in such a way that is does > make use of official buildout APIs. Thanks for the explanation! I agree with you, it would make a lot of sense to use official APIs and not work around them. Don't know how hard that's going to be in this case, though. ;) > Still there's the case that quite some recipes need to be updated to > zc.buildout 1.5.x if they want to use its new features ("system python > support"). Ah. I didn't remember that compattest indeed does generate scripts (I thought it was delegating everything, but that's not correct of course), and I didn't understand from Jan-Jaaps email that system-python-support was a goal here, too, I only got the "some compatibility broke" part and was confused about that. > BTW, I discussed updating the z3c.recipe.i18n for similar reasons - to > support newer buildout features - in a separate thread. There people > seemed to be +1 on releasing a recipe that declares its minimal buildout > version requirement to be >= 1.5.1. Would you say that that situation is > similar to this? Yes, I agree, that makes sense, so +1 from me here. Wolfgang ___ 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 )