Re: [Zope-dev] [Checkins] SVN: z3c.recipe.compattest/trunk/src/z3c/recipe/compattest/runner.py Don't import site on initialization, as this mitigates the buildout 1.5 way of setting sys.path
On 11/26/10 8:37 AM, Michael Howitz wrote: currently the ZTK tests on the trunk do not run successfully in a virtualenv. sip But reverting this change does not help to get the tests of z3c.recipe.compattest itself running again. There are the same errors like before. Is it intensional that ZTK tests fail in virtualenv? What needs be done to get the tests running again in virtualenv? I don't think this was intentional. Then again, I guess it __was__ the intention to make use of the system-python-path-isolation-features in zc.buildout. Personally, I'm not sure where to start fixing this, help and insights appreciated... regards, jw ___ 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] [Checkins] SVN: z3c.recipe.compattest/trunk/src/z3c/recipe/compattest/runner.py Don't import site on initialization, as this mitigates the buildout 1.5 way of setting sys.path
On 11/26/10 10:49 AM, Jan-Wijbrand Kolman wrote: On 11/26/10 8:37 AM, Michael Howitz wrote: currently the ZTK tests on the trunk do not run successfully in a virtualenv. sip But reverting this change does not help to get the tests of z3c.recipe.compattest itself running again. There are the same errors like before. Is it intensional that ZTK tests fail in virtualenv? What needs be done to get the tests running again in virtualenv? I don't think this was intentional. Then again, I guess it __was__ the intention to make use of the system-python-path-isolation-features in zc.buildout. Personally, I'm not sure where to start fixing this, help and insights appreciated... Hmmm, maybe this has been completely obvious to others, but I guess it really boils down to: https://bugs.launchpad.net/virtualenv/+bug/572545 where -S is broken in virtualenvs. Grok's grokproject tool has exactly the same problems, where it doesn't work anymore in a virtualenv *and* we're using -S when calling a newly created project's bootstrap.py. regards,jw ___ 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: 63 OK, 28 Failed
Summary of messages to the zope-tests list. Period Thu Nov 25 13:00:00 2010 UTC to Fri Nov 26 13:00:00 2010 UTC. There were 91 messages: 6 from Zope Tests, 4 from buildbot at pov.lt, 19 from buildbot at winbot.zope.org, 9 from ccomb at free.fr, 53 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Thu Nov 25 14:55:01 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024923.html Subject: FAILED : Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Nov 25 14:59:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024926.html Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:03:20 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024928.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:07:28 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024932.html Subject: FAILED : Zope Buildbot / zope2.13-py2.7 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:07:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024933.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:07:43 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024934.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:07:56 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024935.html Subject: FAILED : Zope Buildbot / zope2.14-py2.7 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:11:07 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024938.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:12:27 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024939.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:15:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024941.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:18:15 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024943.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:20:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024945.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:20:44 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024946.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.7 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:20:54 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024947.html Subject: FAILED : winbot / ztk_dev py_270_win32 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:20:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024948.html Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:23:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024950.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.5 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:31:04 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024952.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:31:17 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024953.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.7 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Nov 25 15:31:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024954.html Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Thu Nov 25 15:33:22 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024956.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.5 slave-osx From: jdriessen at thehealthagency.com Date: Thu Nov 25 16:11:37 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024968.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Thu Nov 25 16:11:51 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-November/024969.html Subject: FAILED : Zope Buildbot / zopetoolkit-py2.7 slave-osx From: jdriessen at thehealthagency.com Date: Thu Nov
Re: [Zope-dev] [Checkins] SVN: z3c.recipe.compattest/trunk/src/z3c/recipe/compattest/runner.py Don't import site on initialization, as this mitigates the buildout 1.5 way of setting sys.path
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/26/2010 04:49 AM, Jan-Wijbrand Kolman wrote: On 11/26/10 8:37 AM, Michael Howitz wrote: currently the ZTK tests on the trunk do not run successfully in a virtualenv. sip But reverting this change does not help to get the tests of z3c.recipe.compattest itself running again. There are the same errors like before. Is it intensional that ZTK tests fail in virtualenv? What needs be done to get the tests running again in virtualenv? I don't think this was intentional. Then again, I guess it __was__ the intention to make use of the system-python-path-isolation-features in zc.buildout. Personally, I'm not sure where to start fixing this, help and insights appreciated... I'd rather shoot the system-python-with-isolation features in the head, myself. Anybody *developing* ZTK should be willing and able to set up either an alternative Python installation or a virtualenv. FWIW, I'm not using zc.buildout = 1.5.0devel anywhere because of the breakage it induces in my normal workflow. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzv14MACgkQ+gerLs4ltQ7KmACeMi+Dza/VQ0J3d5vi77Dahp4I LYYAoK9nP1WlERGGq4dSRllS40QD9Hiv =RIRM -END PGP SIGNATURE- ___ 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 )
