Re: [Zope-dev] Getting back to green
Hello,
On Mon, 17 Oct 2011 10:58:55 -0400 you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/17/2011 10:21 AM, Adam GROSZER wrote:
Hello,
On Mon, 17 Oct 2011 10:08:55 -0400 you wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
We've lost our discipline about keeping the daily tests passing.
I think this is due to two factors:
- - We are running tests for code that nobody is actively
maintaining (e.g., all the 'z3c.*' packages which have been
broken for months).
If you mean the failures on windowze, I think most of them fail on
lxml not having windows egg :-S, someone should kick Sidnei(???)
If the z3c.* packages are being maintained, but not by folks who can
resolve that issue on Windows, then we should do the testing on a
platform where the maintainers *can* get the tests to pass. Having
the board stay red destroys its value for *everybody*, including those
who don't need or care about those packages.
- - Because of the noise of those failures, we've gotten
complacent about seeing multiple failures in the daily test
report, and thus quit trying to find and fix new failures in
code which is maintained.
I would like to propose that we quit reporting test failures for
the unmaintained packages ('zc3.*', for a start. If somebody
really thinks there is value in such testing, we could perhaps
run those tests only weekly (like the others which have
expected failures).
If it's about suppressing the *reporting* then suppress that, not
the test runs please. Just in case someone wants to maintain a
package ;-)
Why waste any resources on tests if nobody is going to find and fix
failures?
Aber hallo, z3c.form is in there. I do *not* think that's not maintained.
Actually I *know* what's the problem, just can't solve it.
Keeping the tests running is like having the *positive* attitude instead
of the dark I don't care.
--
Best regards,
Adam GROSZER
--
Quote of the day:
Drama often obscures the real issues
___
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] [collective.recipe.solrinstance] Example not working
On Mon, Oct 17, 2011 at 8:05 PM, Laurence Rowe l...@lrowe.co.uk wrote: Should we migrate the recipe to github and get a free issue tracker? Ok. I've started the SVN to Git migration. Repo will be at https://github.com/hannosch/collective.recipe.solrinstance and anyone who has recently committed should have contributor rights to the new repo. Andreas: Please add an issue at https://github.com/hannosch/collective.recipe.solrinstance/issues ;) 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] [collective.recipe.solrinstance] Example not working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hanno Schlichting wrote: On Mon, Oct 17, 2011 at 8:05 PM, Laurence Rowe l...@lrowe.co.uk wrote: Should we migrate the recipe to github and get a free issue tracker? Ok. I've started the SVN to Git migration. Repo will be at https://github.com/hannosch/collective.recipe.solrinstance and anyone who has recently committed should have contributor rights to the new repo. Andreas: Please add an issue at https://github.com/hannosch/collective.recipe.solrinstance/issues ;) I am trying to figure out the problem right now. I have now a configuration running with Solr 3.3.0. Apparently more a documentation or configuration bug than a recipe bug... Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJOnWRgAAoJEADcfz7u4AZjvTwLv1nr24jy1a9Vr2ipJY5vq4I0 a7wemSEDrgJOWQb6D6nggQjuEq2ndNhhZp6sSLiYVLsr95UL7GL7tKzYTFujsNLA Wmdw8DzfiHNEPm3Y1L4IpDWeWB4Il9Sl2l6nDlup9EF0hAexVJgua5+zBK7xn7Wc lDfGNZ6a7gfRK9waWl74MdX5aMhQMeOlU48I+N6fuxhzz6K5/VYwxOmA8X9EaAva iJ9nXRqRLVrUzu/tZOwp/6nk0N+pbwl56th1qrJZiUzNHC+1s82PZxWWQwclupjR 6azS+L41RfOyyse0ElYUEOhtWhke/ztcZNS4dYZy09/+4jOKbnHPnyFFyKCcr3oI 1yHItJeKpvyyNARDxs3qLO1a7VNdWzd1PXIWbebzqxYUsgIVBFGaAI/rbFjSXXE6 GBfMm9rhJFZcoObTL0zBADSANh2ch3C1G1dslJ9GK0tdz8xCSch/D1gpA+YimtPc vtUB3e9SXsLF3a9gP3lmKIcPaCCaW6k= =RyeI -END PGP SIGNATURE- attachment: lists.vcf___ 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 - FAILED: 21, OK: 31
This is the summary for test reports received on the zope-tests list between 2011-10-17 00:00:00 UTC and 2011-10-18 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 [1]ZTK 1.0dev / Python2.4.6 Linux 64bit [2]ZTK 1.0dev / Python2.5.5 Linux 64bit [3]ZTK 1.0dev / Python2.6.5 Linux 64bit [4]ZTK 1.1 / Python2.5.5 Linux 64bit [5]ZTK 1.1 / Python2.6.5 Linux 64bit [6]ZTK 1.1 / Python2.7.2 Linux 64bit [7]ZTK 1.1dev / Python2.5.5 Linux 64bit [8]ZTK 1.1dev / Python2.6.5 Linux 64bit [9]ZTK 1.1dev / Python2.7.2 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-2.13-alltests 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_win32 winbot / ZODB_dev py_270_win64 [10] winbot / z3c.authenticator_py_265_32 [11] winbot / z3c.baseregistry_py_265_32 [12] winbot / z3c.contents_py_265_32 [13] winbot / z3c.form_py_265_32 [14] winbot / z3c.formui_py_265_32 [15] winbot / z3c.jsontree_py_265_32 [16] winbot / z3c.layer.pagelet_py_265_32 [17] winbot / z3c.layer.ready2go_py_265_32 [18] winbot / z3c.macro_py_265_32 [19] winbot / z3c.pagelet_py_265_32 [20] winbot / z3c.tabular_py_265_32 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 [21] 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]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051301.html [2]FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051299.html [3]FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051300.html [4]FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051346.html [5]FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051345.html [6]FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051344.html [7]FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051302.html [8]FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051304.html [9]FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051303.html [10] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051316.html [11] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051314.html [12] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051313.html [13] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051308.html [14] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051309.html [15] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051315.html [16] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051311.html [17] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051319.html [18] FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051317.html [19] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051318.html [20] FAILED winbot / z3c.tabular_py_265_32
