zope-tests - FAILED: 9, OK: 72
This is the summary for test reports received on the zope-tests list between 2011-06-03 00:00:00 UTC and 2011-06-04 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 ---------------- Bluebream / Python2.4.6 64bit linux Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.5 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 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 Buildbot / zope2.12-py2.6 slave-ubuntu32 Zope Buildbot / zope2.12-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 Zope Buildbot / zope2.13-py2.6 slave-ubuntu64 Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 [1] Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 Zope Buildbot / zope2.13_win-py2.6 slave-win Zope Buildbot / zope2.13_win-py2.7 slave-win Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 [2] Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 Zope Buildbot / zopetoolkit_win-py2.5 slave-win Zope Buildbot / zopetoolkit_win-py2.6 slave-win 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 [3] winbot / z3c.coverage_py_265_32 [4] winbot / z3c.rml_py_265_32 [5] winbot / zc_buildout_dev py_254_win32 [6] winbot / zc_buildout_dev py_265_win32 [7] winbot / zc_buildout_dev py_265_win64 [8] winbot / zc_buildout_dev py_270_win32 [9] winbot / zc_buildout_dev py_270_win64 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 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 Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html [2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html [3] FAILED winbot / z3c.coverage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-June/042522.html [4] FAILED winbot / z3c.rml_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-June/042521.html [5] FAILED winbot / zc_buildout_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-June/042579.html [6] FAILED winbot / zc_buildout_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-June/042580.html [7] FAILED winbot / zc_buildout_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-June/042581.html [8] FAILED winbot / zc_buildout_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-June/042582.html [9] FAILED winbot / zc_buildout_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-June/042583.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
[1] FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html
[2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html
These two are both the "segfault-at-exit" issue. 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/ iEYEARECAAYFAk3rr3oACgkQ+gerLs4ltQ7S5wCeOlLJiSalEwFi78KxTwdWYhBW jHMAoIVtBwTjbGgVpAsA/oltZkYoOqDG =qHVi -----END PGP SIGNATURE-----
On Sun, Jun 5, 2011 at 6:31 PM, Tres Seaver <tseaver@palladion.com> wrote:
[1] FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html
[2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html
These two are both the "segfault-at-exit" issue.
I finally took the time to install me a virtual machine with Ubuntu 64bit on it. And I was able to reproduce the issue! It's not a segfault at exit, but actually happens inside a test: test_interfaces (Acquisition.tests) (0.001 s) test_mixed_explicit_and_explicit (Acquisition.tests)Segmentation fault Or to get the issue quicker: $ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault I haven't yet tried to debug the problem itself. Hanno
On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
Or to get the issue quicker:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
I haven't yet tried to debug the problem itself.
Here's some more info: The last successful build was #256 on Wed Apr 27 02:06:59 2011 which build revision 121465 The first failing build was #257 on Wed Apr 27 15:19:46 2011 which build revision 121473 Looking at the SVN changelog of Zope trunk, there were changes in r121460 and r121502. So the two builds used the exact same code, but still produced a different result. So it must be a change in the config of the buildslave that triggered this. There's no Python 2.7 release anywhere close to April this year, so I'm pretty sure both builds used the same Python 2.7.1. What caused the failure is a mystery to me. Hanno
On Sun, Jun 5, 2011 at 8:57 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
Here's some more info:
The last successful build was #256 on Wed Apr 27 02:06:59 2011 which build revision 121465 The first failing build was #257 on Wed Apr 27 15:19:46 2011 which build revision 121473
Looking at the SVN changelog of Zope trunk, there were changes in r121460 and r121502.
So the two builds used the exact same code, but still produced a different result. So it must be a change in the config of the buildslave that triggered this. There's no Python 2.7 release anywhere close to April this year, so I'm pretty sure both builds used the same Python 2.7.1.
What caused the failure is a mystery to me.
I see that Jan-Jaap did some unrelated changes to the buildslave config on that day (http://zope3.pov.lt/trac/changeset/121467/Sandbox/janjaapdriessen/buildbot). Jan-Jaap: Do you remember doing anything else on that day? Like upgrading the operating system, installing new OS packages or anything that could cause the sudden failure? Hanno
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/05/2011 02:24 PM, Hanno Schlichting wrote:
On Sun, Jun 5, 2011 at 6:31 PM, Tres Seaver <tseaver@palladion.com> wrote:
[1] FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html
[2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html
These two are both the "segfault-at-exit" issue.
I finally took the time to install me a virtual machine with Ubuntu 64bit on it. And I was able to reproduce the issue!
It's not a segfault at exit, but actually happens inside a test:
test_interfaces (Acquisition.tests) (0.001 s) test_mixed_explicit_and_explicit (Acquisition.tests)Segmentation fault
Or to get the issue quicker:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
I haven't yet tried to debug the problem itself.
I cannot reproduce on my "native" Ubuntu x86_64 machine using a built-from-scratch Python 2.7.1:: - -------------------------- %< ----------------------------- $ uname -a Linux xxx.example.com 2.6.32-31-server #61-Ubuntu SMP Fri Apr 8 19:44:42 UTC 2011 x86_64 GNU/Linux $ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk Z2 ... $ cd Z2 $ /opt/Python-2.7.1/bin/python bootstrap.py && bin/buildout ... $ bin/alltests ... Running OFS.tests.testCopySupportEvents.EventLayer tests: Set up OFS.tests.testCopySupportEvents.EventLayer in 0.094 seconds. Ran 14 tests with 0 failures and 0 errors in 0.042 seconds. Running OFS.tests.testCopySupportHooks.HookLayer tests: Tear down OFS.tests.testCopySupportEvents.EventLayer in 0.000 seconds. Set up OFS.tests.testCopySupportHooks.HookLayer in 0.094 seconds. Ran 14 tests with 0 failures and 0 errors in 0.044 seconds. Running Testing.ZopeTestCase.layer.ZopeLite tests: Tear down OFS.tests.testCopySupportHooks.HookLayer in 0.000 seconds. Set up Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Ran 220 tests with 0 failures and 0 errors in 4.660 seconds. Running Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer tests: Set up Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.002 seconds. Ran 18 tests with 0 failures and 0 errors in 0.027 seconds. Running Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer tests: Tear down Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.001 seconds. Set up Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Ran 2 tests with 0 failures and 0 errors in 0.005 seconds. Running zope.testrunner.layer.UnitTests tests: Tear down Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Ran 2492 tests with 0 failures and 0 errors in 44.382 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. Total: 2760 tests, 0 failures, 0 errors in 50.124 seconds. - -------------------------- %< ----------------------------- 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/ iEYEARECAAYFAk3s6LYACgkQ+gerLs4ltQ4+LQCgrb7gVVmL41An8qCaKO0Bhww+ RG0AoI39SQwpYLs3v0K3APkp0ovZt74d =mtma -----END PGP SIGNATURE-----
On 6/6/11 16:48 , Tres Seaver wrote:
On 06/05/2011 02:24 PM, Hanno Schlichting wrote:
On Sun, Jun 5, 2011 at 6:31 PM, Tres Seaver <tseaver@palladion.com> wrote:
[1] FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042535.html
[2] FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-June/042537.html
These two are both the "segfault-at-exit" issue.
I finally took the time to install me a virtual machine with Ubuntu 64bit on it. And I was able to reproduce the issue!
It's not a segfault at exit, but actually happens inside a test:
test_interfaces (Acquisition.tests) (0.001 s) test_mixed_explicit_and_explicit (Acquisition.tests)Segmentation fault
Or to get the issue quicker:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
I haven't yet tried to debug the problem itself.
I cannot reproduce on my "native" Ubuntu x86_64 machine using a built-from-scratch Python 2.7.1::
On the specific buildslave machine I tested with a python-2.7 built from scratch, re-ran bootstrap.py, bin/buildout, bin/alltests and all tests passed. It seems the python-2.7 from the "deadsnakes" PPA that is installed on this buildmachine behaves badly. I do not know why, and I do not really feel like investigating it. I'll remove the python-2.7 PPA install from this machine we'll start using the hand-build python-2.7 instead. regards, jw
On Wed, Jun 8, 2011 at 1:08 PM, Jan-Wijbrand Kolman <janwijbrand@gmail.com> wrote:
It seems the python-2.7 from the "deadsnakes" PPA that is installed on this buildmachine behaves badly. I do not know why, and I do not really feel like investigating it. I'll remove the python-2.7 PPA install from this machine we'll start using the hand-build python-2.7 instead.
The Python from PPA wasn't at fault here. It seems it just exhibits a rare configuration where sizeof(int) != sizeof(pointer). Please feel free to move back to the PPA build. I fixed the real issue in the code. Hanno
On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
I haven't yet tried to debug the problem itself.
I took the time to investigate this. It came down to the same issue noted in https://bugs.launchpad.net/bugs/675064. Some code treated a C int as a pointer. Apparently on most platforms sizeof(int) == sizeof(pointer), but there's some where that's not the case. In this particular case it was a simple mistake of using the wrong variable: PyObject *expl=0; int explicit=1; UNLESS (PyArg_ParseTupleAndKeywords( args, kw, "O|OOOOi", acquire_args+1, &name, &filter, &extra, &explicit, &defalt, &containment )) return NULL; if (expl) explicit=PyObject_IsTrue(expl); The fix was to pass &expl instead of &explicit into PyArg_ParseTupleAndKeywords. Almost the same code existed in Wrapper_acquire_method and module_aq_acquire and only Wrapper_acquire_method got it wrong. I released a new Acquisition version and put it into Zope 2.x. Hopefully the buildbots will finally get green again. Hanno
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/11/2011 11:36 AM, Hanno Schlichting wrote:
On Sun, Jun 5, 2011 at 8:24 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
$ bin/alltests -s Acquisition -t test_mixed_explicit_and_explicit Running zope.testrunner.layer.UnitTests tests: Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Segmentation fault
I haven't yet tried to debug the problem itself.
I took the time to investigate this. It came down to the same issue noted in https://bugs.launchpad.net/bugs/675064. Some code treated a C int as a pointer. Apparently on most platforms sizeof(int) == sizeof(pointer), but there's some where that's not the case.
In this particular case it was a simple mistake of using the wrong variable:
PyObject *expl=0; int explicit=1;
UNLESS (PyArg_ParseTupleAndKeywords( args, kw, "O|OOOOi", acquire_args+1, &name, &filter, &extra, &explicit, &defalt, &containment )) return NULL;
if (expl) explicit=PyObject_IsTrue(expl);
The fix was to pass &expl instead of &explicit into PyArg_ParseTupleAndKeywords. Almost the same code existed in Wrapper_acquire_method and module_aq_acquire and only Wrapper_acquire_method got it wrong.
I released a new Acquisition version and put it into Zope 2.x. Hopefully the buildbots will finally get green again.
Excellent! Thanks very much for tracking the beast to its lair and aq_wrenching of its arm (now we just need to watch out for its mother ;) 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/ iEYEARECAAYFAk3zjhIACgkQ+gerLs4ltQ5KSgCgqGXWqmpqbPJiolsWjLY9nGmM xyUAoIZBc5acuHPzpiY/WV9wqtOYX0l1 =wIQ8 -----END PGP SIGNATURE-----
participants (4)
-
Hanno Schlichting -
Jan-Wijbrand Kolman -
Tres Seaver -
Zope tests summarizer