[Zope-dev] Zope Tests: 71 OK, 16 Failed

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/28/2011 06:58 AM, Zope Tests Summarizer wrote:

> Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
> From: jdriessen at thehealthagency.com
> Date: Sun Feb 27 10:06:05 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033318.html

This is an build failure:  tests fail with import errors for BTrees, but
the "buildout" step does not show failure.


> Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit
> From: ccomb at free.fr
> Date: Sun Feb 27 22:13:21 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033369.html
> 
> Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit
> From: ccomb at free.fr
> Date: Sun Feb 27 22:13:54 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033370.html
> 
> Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit
> From: ccomb at free.fr
> Date: Sun Feb 27 22:14:06 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033371.html

The ZTK 1.0 dev builds blow up inside the "unit" tests for
zope.app.server, where one of the tests appears to hang, but not produce
output:

- ---------------------- %< ------------------------
$ svn co $ZSVN/zopetoolkit/branches/1.0 ztk-1.0
$ cd ztk-1.0
$ /opt/Python-2.6.5/bin/python bootstrap && bin/buildout
...
$ bin/test-zopeapp-zope.app.server
<all tests pass>
$ bin/develop -c "zope.app.server" && bin/buildout
...
$ bin/test-zopeapp-zope.app.server
<all tests still pass>
$ bin/develop -c "zope.*" && bin/buildout
$ bin/test-zopeapp-zope.app.server -vvD
...
Running zope.testing.testrunner.layer.UnitTests tests:
  Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
  Running:
 test_config_without_handlers
(zope.app.server.tests.test_accesslog.TestAccessLogging)
...
 test_get_password_manager
(zope.app.server.tests.test_mkzopeinstance.InputCollectionTestCase)
- ---------------------- %< ------------------------

I hope that is enough information for somebody who knows the zope.app
code to fix the tests.  If not, I suggest we drop the ZTK 1.0 tests,
given that we aren't changing that package set actively, and that we
don't have resources to keep the tests green.


> Subject: FAILED : winbot / z3c.form_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 22:26:08 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033372.html
> 
> Subject: FAILED : winbot / z3c.rml_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 22:50:50 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033373.html
> 
> Subject: FAILED : winbot / z3c.template_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 22:59:35 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033374.html
> 
> Subject: FAILED : winbot / z3c.layer.ready2go_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:05:09 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033376.html
> 
> Subject: FAILED : winbot / z3c.formui_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:06:47 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033377.html
> 
> Subject: FAILED : winbot / z3c.tabular_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:09:10 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033378.html
> 
> Subject: FAILED : winbot / z3c.contents_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:10:09 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033379.html
> 
> Subject: FAILED : winbot / z3c.ptcompat_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:28:15 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033380.html
> 
> Subject: FAILED : winbot / z3c.pdftemplate_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:32:28 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033381.html
> 
> Subject: FAILED : winbot / z3c.coverage_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:33:48 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033382.html
> 
> Subject: FAILED : winbot / z3c.macro_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:34:49 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033383.html
> 
> Subject: FAILED : winbot / z3c.pagelet_py_265_32
> From: buildbot at winbot.zope.org
> Date: Sun Feb 27 23:39:04 EST 2011
> URL: http://mail.zope.org/pipermail/zope-tests/2011-February/033384.html


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.



Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at 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/

iEYEARECAAYFAk1r20YACgkQ+gerLs4ltQ4qpACgquvggBLZNx5Q1oyW6QSGfbY5
jVwAn0CC5jdabaEUKSi4g8YuWvjXM1Ck
=mTTk
-----END PGP SIGNATURE-----