zope-tests - FAILED: 21, OK: 31
This is the summary for test reports received on the zope-tests list between 2011-10-18 00:00:00 UTC and 2011-10-19 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/051353.html [2] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051351.html [3] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051352.html [4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051398.html [5] FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051397.html [6] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051396.html [7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html [8] FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051356.html [9] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051355.html [10] FAILED winbot / z3c.authenticator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051368.html [11] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051366.html [12] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051365.html [13] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051360.html [14] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051361.html [15] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051367.html [16] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051363.html [17] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051371.html [18] FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051369.html [19] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051370.html [20] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051364.html [21] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[1] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051353.html
[2] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051351.html
[3] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051352.html
These
are all failing due to a missing version pin for 'six', which should not happen: the ZTK 1.0 package set should not include the new version of 'zope.schema' which introduced this dependency.
[4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051398.html
[5] FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051397.html
[6] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051396.html
This
failure is due to the unexpected presence of a 'Data.fs' file in what is supposed to be a newly-created tempdir. I don't understand how that is supposed to work, but the bug seems real.
[7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html
Syntax
errors due to Py3k compatibility changes in 'zope.schema'. The "ZTK 1.1dev" checkouts pull in the trunk of 'zope.schema', which is now backward-incompatible (it drops support for Python 2.5). I think we should be creating a '3.8' branch of 'zope.schema' (copied from 3.8.1), and make the "ZTK 1.1dev" checkout use that. Meanwhile, I think we should update the 'zope.schema' trunk to indicate that it is targeting a new major version, 4.0, due to new dependencies and dropping Python 2.5 compatibility.
[8] FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051356.html
There
is an odd 'zope.testrunner' failure here: Usage: test [options] [MODULE] [TEST] test: error: option --profile: invalid choice: 'cProfile' (choose from ) Failure in test /home/ccomb/ztk1.1dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testrunner/src/zope/testrunner/testrunner-subunit.txt Failed doctest test for testrunner-subunit.txt And also the "unexpected Data.fs" issue which affected #4, 5, and 6.
[9] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051355.html
This
is the "unexpected Data.fs" issue which affected #4, 5, and 6. I'm ignoring the 'z3c.*' failures: I still want these tests either fixed or else dropped from the daily report.
[21] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html
This
is the same Python 2.5 incompatibility problem which afflicts #7. 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/ iEYEARECAAYFAk6gRRAACgkQ+gerLs4ltQ7/DwCePrkkEc0JzRq5ukPaPpvgx/YC MZ4Anj0IM4SH/uWPnvVVOXbtO2fBCEfu =rxze -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/20/2011 11:58 AM, Tres Seaver wrote:
[7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html
Syntax errors due to Py3k compatibility changes in 'zope.schema'. The "ZTK 1.1dev" checkouts pull in the trunk of 'zope.schema', which is now backward-incompatible (it drops support for Python 2.5). I think we should be creating a '3.8' branch of 'zope.schema' (copied from 3.8.1), and make the "ZTK 1.1dev" checkout use that. Meanwhile, I think we should update the 'zope.schema' trunk to indicate that it is targeting a new major version, 4.0, due to new dependencies and dropping Python 2.5 compatibility.
Both ZTK 1.0 and 1.1 include zope.schema 3.7.1. I just made a '3.7' branch, copying from the '3.7.1' tag, and updated the 'ztk.cfg' for both ZTK branches to use it, rather than the 'zope.schema' trunk. 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/ iEYEARECAAYFAk6gSlcACgkQ+gerLs4ltQ4JYACfX/1UncaAc9maneofMz9Mwezu iCoAn2DDHh/EVnVC+AvS2+2Wx+wbR1dV =fU6h -----END PGP SIGNATURE-----
On Thu, Oct 20, 2011 at 11:58:09AM -0400, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[1] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051353.html
[2] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051351.html
[3] FAILED ZTK 1.0dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051352.html
These
are all failing due to a missing version pin for 'six', which should not happen: the ZTK 1.0 package set should not include the new version of 'zope.schema' which introduced this dependency.
[4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051398.html
[5] FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051397.html
[6] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051396.html
This
failure is due to the unexpected presence of a 'Data.fs' file in what is supposed to be a newly-created tempdir. I don't understand how that is supposed to work, but the bug seems real.
[7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051354.html
Syntax
errors due to Py3k compatibility changes in 'zope.schema'. The "ZTK 1.1dev" checkouts pull in the trunk of 'zope.schema', which is now backward-incompatible (it drops support for Python 2.5). I think we should be creating a '3.8' branch of 'zope.schema' (copied from 3.8.1), and make the "ZTK 1.1dev" checkout use that.
Thanks for fixing these. I didn't realize that the buildouts would break because of my change. I should have though. (I've also given up looking at the buildout perma-failures a long time ago)
Meanwhile, I think we should update the 'zope.schema' trunk to indicate that it is targeting a new major version, 4.0, due to new dependencies and dropping Python 2.5 compatibility.
I've done this.
[8] FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051356.html
There
is an odd 'zope.testrunner' failure here:
Usage: test [options] [MODULE] [TEST]
test: error: option --profile: invalid choice: 'cProfile' (choose from )
Failure in test /home/ccomb/ztk1.1dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testrunner/src/zope/testrunner/testrunner-subunit.txt Failed doctest test for testrunner-subunit.txt
And also the "unexpected Data.fs" issue which affected #4, 5, and 6.
[9] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051355.html
This
is the "unexpected Data.fs" issue which affected #4, 5, and 6.
I'm ignoring the 'z3c.*' failures: I still want these tests either fixed or else dropped from the daily report.
[21] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html
This
is the same Python 2.5 incompatibility problem which afflicts #7.
This is a tricky issue, there are 2 parts: * Supporting python 2.5 in zope.schema is not hard, but will make the code quite ugly (no class decorator for implements) * I'm not sure if the next version of the ZTK will need to support Python 2.5 So there seem to be 3 options to fix this buildout issue: 1. Point the ZTK trunk at the zope.schema 3.8 branch 2. Make the zope.schema code uglier and support 2.5 3. Declare that the next ZTK version drops support for 2.5 and stop the buildbot for Python 2.5 + ZTK trunk I'm partial to option 1 to get the buildbot working and defer the Python 2.5/ugly code decision to later. -- Brian Sutherland
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/24/2011 07:24 AM, Brian Sutherland wrote:
On Thu, Oct 20, 2011 at 11:58:09AM -0400, Tres Seaver wrote:
Syntax errors due to Py3k compatibility changes in 'zope.schema'. The "ZTK 1.1dev" checkouts pull in the trunk of 'zope.schema', which is now backward-incompatible (it drops support for Python 2.5). I think we should be creating a '3.8' branch of 'zope.schema' (copied from 3.8.1), and make the "ZTK 1.1dev" checkout use that.
Thanks for fixing these. I didn't realize that the buildouts would break because of my change. I should have though.
(I've also given up looking at the buildout perma-failures a long time ago)
We should probably look at *all* '/trunk' dependencies in the ZTK as future sources of such problems: people working on trunk development know that the released ZTK pins versions, but may not realize that the '-dev' checkouts are possibly affected. Preemptively switching ZTK dev checkouts to use only release branches would make that problem go away, but at the cost of requiring bugfix-only changes to be backported: today, in many packages, the trunk remains identical to a "release branch" for a long time. Rather than such a drastic step, I think we need to adopt a new policy that the developer who makes the first "non-bugfix" change to the trunk (i.e., adding a new feature or dependency, a backward-incompatibility, or dropping support for a Python version) is also responsible for finding an fixing any ZTK breakage (e.g., by creating the release branch and changing the ZTK configuration to use it).
[21] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-October/051382.html
This is the same Python 2.5 incompatibility problem which afflicts #7.
This is a tricky issue, there are 2 parts:
* Supporting python 2.5 in zope.schema is not hard, but will make the code quite ugly (no class decorator for implements) * I'm not sure if the next version of the ZTK will need to support Python 2.5
So there seem to be 3 options to fix this buildout issue:
1. Point the ZTK trunk at the zope.schema 3.8 branch 2. Make the zope.schema code uglier and support 2.5 3. Declare that the next ZTK version drops support for 2.5 and stop the buildbot for Python 2.5 + ZTK trunk
I'm partial to option 1 to get the buildbot working and defer the Python 2.5/ugly code decision to later.
I also prefer that we drop 2.5 compatibility on the ZTK trunk. The 2.5.6 release page says[1]: This release is most likely the final release of Python 2.5; under the current release policy, no security issues in Python 2.5 will be fixed after October, 2011. [1] http://www.python.org/download/releases/2.5.6/ 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/ iEYEARECAAYFAk6lf24ACgkQ+gerLs4ltQ53lgCcCAuxGG5Up+0XfFRquXyaLxtK XiMAnjhY+HzfjTddr3afk8kk66U345C/ =BJmV -----END PGP SIGNATURE-----
On Mon, Oct 24, 2011 at 5:08 PM, Tres Seaver <tseaver@palladion.com> wrote:
I also prefer that we drop 2.5 compatibility on the ZTK trunk. The 2.5.6 release page says[1]:
This release is most likely the final release of Python 2.5; under the current release policy, no security issues in Python 2.5 will be fixed after October, 2011.
Fine by me. We have ZTK 1.1 which can keep Python 2.5 support. For Zope 2, we have dropped Python 2.5 long ago and only do Python 2.6 and 2.7 these days. Hanno
participants (4)
-
Brian Sutherland -
Hanno Schlichting -
Tres Seaver -
Zope tests summarizer