Summary of messages to the zope-tests list. Period Tue Oct 5 12:00:00 2010 UTC to Wed Oct 6 12:00:00 2010 UTC. There were 50 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 20 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 9 from jdriessen at thehealthagency.com. Test failures ------------- Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:19:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021120.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:28:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021121.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:37:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021122.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:46:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021123.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:56:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021124.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:21:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021127.html Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:43:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021136.html Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Oct 6 05:19:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021169.html Tests passed OK --------------- Subject: OK : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:06:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021125.html Subject: OK : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:14:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021126.html Subject: OK : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:23:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021128.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:26:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021129.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:28:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021130.html Subject: OK : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:31:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021131.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:32:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021132.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:33:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021133.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:35:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021134.html Subject: OK : Zope Buildbot / ztk slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:39:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021135.html Subject: OK : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:53:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021137.html Subject: OK : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 18:04:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021138.html Subject: OK : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 18:16:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021139.html Subject: OK : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 18:28:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021140.html Subject: OK : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 18:39:07 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021141.html Subject: OK : winbot / ZODB_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 19:35:51 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021142.html Subject: OK : ZTK 1.0 / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 19:42:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021143.html Subject: OK : ZTK 1.0 / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 19:42:34 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021144.html Subject: OK : ZTK 1.0 / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 19:42:42 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021145.html Subject: OK : winbot / ZODB_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 20:32:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021146.html Subject: OK : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Tue Oct 5 21:11:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021147.html Subject: OK : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 21:29:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021148.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 5 21:30:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021149.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 5 21:32:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021150.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Tue Oct 5 21:34:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021151.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Tue Oct 5 21:36:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021152.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Tue Oct 5 21:38:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021153.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Tue Oct 5 21:40:54 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021154.html Subject: OK : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Tue Oct 5 21:59:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021155.html Subject: OK : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 22:02:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021156.html Subject: OK : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 22:04:09 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021157.html Subject: OK : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Tue Oct 5 22:04:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021158.html Subject: OK : Bluebream / Python2.4.6 64bit linux From: ccomb at free.fr Date: Tue Oct 5 22:04:56 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021159.html Subject: OK : Bluebream / Python2.6.5 64bit linux From: ccomb at free.fr Date: Tue Oct 5 22:05:00 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021160.html Subject: OK : Bluebream / Python2.5.5 64bit linux From: ccomb at free.fr Date: Tue Oct 5 22:05:01 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021161.html Subject: OK : Zope 3.4 Known Good Set / py2.5-64bit-linux From: buildbot at pov.lt Date: Tue Oct 5 22:10:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021162.html Subject: OK : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 22:25:33 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021163.html Subject: OK : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Tue Oct 5 23:00:59 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021164.html Subject: OK : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 23:22:46 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021165.html Subject: OK : Zope 3.4 KGS / Python2.4.6 64bit linux From: ccomb at free.fr Date: Wed Oct 6 00:21:13 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021166.html Subject: OK : Zope 3.4 KGS / Python2.5.5 64bit linux From: ccomb at free.fr Date: Wed Oct 6 00:42:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021167.html Subject: OK : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Oct 6 05:06:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021168.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The first five failures appear to be related to the same cause.
Test failures -------------
Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:19:16 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021120.html
Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:28:02 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021121.html
Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:37:24 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021122.html
This appears to be a newline normalization issue in the doctests for zope.testrunner: somebody who can test a fix on both Windows and non-Windows should look at the flags passed to the failing tests.
Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:46:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021123.html
Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Oct 5 16:56:23 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021124.html
Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:21:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021127.html
I couldn't view the test output on this one: the URL yields a 404.
Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:43:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021136.html
This one seems to be a non-Windows-specific zc.buildout test failure: I don't think we run those tests anywhere else.
Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Oct 6 05:19:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021169.html
The link for this one also 404s. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@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/ iEYEARECAAYFAkysg6QACgkQ+gerLs4ltQ7+AQCghNWEsha21L2liCrnT57A7qCw iUwAnj1o3kQH0du7P6iDhknlNVI8H6dJ =xvng -----END PGP SIGNATURE-----
On 6 October 2010 16:11, Tres Seaver <tseaver@palladion.com> wrote: snip
Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Tue Oct 5 17:21:43 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021127.html
I couldn't view the test output on this one: the URL yields a 404.
My bad. I am upgrading this buildbot (more packages, python2.7). Back online soon.
Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:43:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021136.html
This one seems to be a non-Windows-specific zc.buildout test failure: I don't think we run those tests anywhere else.
Subject: FAILED : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Oct 6 05:19:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021169.html
The link for this one also 404s.
Same same.
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com
Hello Tres,
Subject: FAILED : winbot / zc_buildout_dev py_244_win32 From: buildbot at winbot.zope.org Date: Tue Oct 5 17:43:39 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-October/021136.html
TS> This one seems to be a non-Windows-specific zc.buildout test failure: I TS> don't think we run those tests anywhere else. Gary personally said about windows+python 2.4+zc.buildout: Just don't ask me. Either we just ignore this or I drop python 2.4. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: As sure as God puts His children in the furnace of affliction, He will be with them in it. - Charles Haddon Spurgeon
On Wed, Oct 6, 2010 at 6:02 PM, Adam GROSZER <agroszer@gmail.com> wrote:
Gary personally said about windows+python 2.4+zc.buildout: Just don't ask me. Either we just ignore this or I drop python 2.4.
At least for zc,buildout 1.5+ I'd be fine to drop Python 2.4 test runs. We don't have zc.buildout in the ZTK 1.0, so it's fine not to support it. Hanno
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/06/2010 12:30 PM, Hanno Schlichting wrote:
On Wed, Oct 6, 2010 at 6:02 PM, Adam GROSZER <agroszer@gmail.com> wrote:
Gary personally said about windows+python 2.4+zc.buildout: Just don't ask me. Either we just ignore this or I drop python 2.4.
At least for zc,buildout 1.5+ I'd be fine to drop Python 2.4 test runs. We don't have zc.buildout in the ZTK 1.0, so it's fine not to support it.
+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. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@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/ iEYEARECAAYFAkyspOgACgkQ+gerLs4ltQ7FTgCfZMJ47mJI0nHpxEHbS02qln3L N0IAoJS3uXkySg+vQmktPS9GHgh441Br =2TH1 -----END PGP SIGNATURE-----
-----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. 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. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkytbjkACgkQRAx5nvEhZLJ+2wCcCo19KDbb0gWvz6L4K0ggilIg zvAAoISUrp6R9dhMn5S3aTXdb2j3GXjc =VG5q -----END PGP SIGNATURE-----
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.
On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman <wichert@wiggy.net> 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
On 10/7/10 11:09 , Patrick Gerken wrote:
On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman<wichert@wiggy.net> 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.
On Thu, Oct 7, 2010 at 11:22 AM, Wichert Akkerman <wichert@wiggy.net> 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
On 10/7/10 11:26 , Hanno Schlichting wrote:
On Thu, Oct 7, 2010 at 11:22 AM, Wichert Akkerman<wichert@wiggy.net> 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.
On Thu, Oct 7, 2010 at 11:28, Wichert Akkerman <wichert@wiggy.net> 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
On 10/7/10 11:35 , Patrick Gerken wrote:
On Thu, Oct 7, 2010 at 11:28, Wichert Akkerman<wichert@wiggy.net> 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.
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.
Hi! Patrick Gerken wrote:
On Thu, Oct 7, 2010 at 10:50, Wichert Akkerman<wichert@wiggy.net> 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
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
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 · ct@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
participants (11)
-
Adam GROSZER -
Christian Theune -
Hanno Schlichting -
Jan-Jaap Driessen -
Jens Vagelpohl -
Marius Gedminas -
Patrick Gerken -
Tres Seaver -
Wichert Akkerman -
yuppie -
Zope Tests Summarizer