Hi everybody Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds. The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux? Regards Roger Ineichen _____________________________ END OF MESSAGE
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
Work on my Linux box (Ubuntu 8.10, w/ Python 2.5): - -------------------------- %< --------------------------- $ svn co $ZSVN/zc.buildout/trunk zc.buildout-trunk U zc.buildout-trunk/CHANGES.txt U zc.buildout-trunk/setup.py U zc.buildout-trunk/zc.recipe.egg_/CHANGES.txt U zc.buildout-trunk/zc.recipe.egg_/setup.py U zc.buildout-trunk/zc.recipe.egg_/src/zc/recipe/egg/egg.py U zc.buildout-trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt U zc.buildout-trunk/dev.py U zc.buildout-trunk/src/zc/buildout/testing.py U zc.buildout-trunk/src/zc/buildout/buildout.txt U zc.buildout-trunk/src/zc/buildout/easy_install.txt U zc.buildout-trunk/src/zc/buildout/easy_install.py Checked out revision 99446. $ cd zc.buildout-trunk/ $ ls bin buildout.cfg dev.py doc.txt README.txt src bootstrap CHANGES.txt dist eggs setup.py todo.txt build develop-eggs doc parts specifications zc.recipe.egg_ $ /path/to/virtualenv-2.5 --no-site-packages /tmp/zcb ... $ /tmp/zcb/bin/python bootstrap/bootstrap.py ... $ bin/buildout ... $ bin/test ... Ran 373 tests with 0 failures and 0 errors in 2 minutes 58.273 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ8Tv/+gerLs4ltQ4RAq7wAKCriyQU/yX5vFd5xP7PKeAJ6ecVFwCglxVL nuuvOIhUi8fFDX6b63B/+6c= =QEqP -----END PGP SIGNATURE-----
Hi Tres
Betreff: Re: [Zope-dev] zc.buildout broken
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
Work on my Linux box (Ubuntu 8.10, w/ Python 2.5):
- -------------------------- %< --------------------------- $ svn co $ZSVN/zc.buildout/trunk zc.buildout-trunk U zc.buildout-trunk/CHANGES.txt U zc.buildout-trunk/setup.py U zc.buildout-trunk/zc.recipe.egg_/CHANGES.txt U zc.buildout-trunk/zc.recipe.egg_/setup.py U zc.buildout-trunk/zc.recipe.egg_/src/zc/recipe/egg/egg.py U zc.buildout-trunk/zc.recipe.egg_/src/zc/recipe/egg/README.txt U zc.buildout-trunk/dev.py U zc.buildout-trunk/src/zc/buildout/testing.py U zc.buildout-trunk/src/zc/buildout/buildout.txt U zc.buildout-trunk/src/zc/buildout/easy_install.txt U zc.buildout-trunk/src/zc/buildout/easy_install.py Checked out revision 99446. $ cd zc.buildout-trunk/ $ ls bin buildout.cfg dev.py doc.txt README.txt src bootstrap CHANGES.txt dist eggs setup.py todo.txt build develop-eggs doc parts specifications zc.recipe.egg_ $ /path/to/virtualenv-2.5 --no-site-packages /tmp/zcb ... $ /tmp/zcb/bin/python bootstrap/bootstrap.py ... $ bin/buildout ... $ bin/test ... Ran 373 tests with 0 failures and 0 errors in 2 minutes 58.273 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds. - -------------------------- %< ---------------------------
Thanks a lot. I'll take another look at what happens on windows. Regards Roger Ineichen
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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ8Tv/+gerLs4ltQ4RAq7wAKCriyQU/yX5vFd5xP7PKeAJ6ecVFwCglxVL nuuvOIhUi8fFDX6b63B/+6c= =QEqP -----END PGP SIGNATURE-----
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Roger Ineichen wrote:
Thanks a lot. I'll take another look at what happens on windows.
More info on the errors would certainly be interesting... I believe Jim prefers the distutils-sig mailing list for buildout-related stuff nowadays, you may get a response from him there... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Fri, Apr 24, 2009 at 05:56:45AM +0200, Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
It is always interesting to see the failures, but attaching large log files to emails is not very polite. Solution: use a pastebin. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
On Fri, 24 Apr 2009 13:10:30 +0200, Marius Gedminas wrote:
On Fri, Apr 24, 2009 at 05:56:45AM +0200, Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
It is always interesting to see the failures, but attaching large log files to emails is not very polite.
True for large files, but a traceback is not that large _imo_. Depends on your connection of course. Also, we are on a development list, so if somewhere, then here tracebacks are on topic.
Solution: use a pastebin.
I disagree: pastebin is good for linking from irc, but when I come back to the archive I would like to see the details even when the pastebin entry is gone. -- Balazs Ree
Hi all, thanks for the Feedback.... Here is a pastebin link. Posting to a mailinglist is defently to bad for this 4572 lines of traceback ;-) http://pastebin.com/f1adc7a43 I think there are different things wrong. The first error looks like a difference in linux and windows output: ---------------------------------------------------------------------- File "d:\eggdev\source\zc\zc.buildout\trunk\src\zc\buildout\buildout.txt", line 55, in buildout.txt Failed example: ls(sample_buildout, 'eggs') Expected: setuptools.egg - zc.buildout.egg Got: - setuptools.egg-link - zc.buildout.egg Other errors look like a path encoding problem because there is no difference if I compare: ---------------------------------------------------------------------- File "d:\eggdev\source\zc\zc.buildout\trunk\src\zc\buildout\buildout.txt", line 287, in buildout.txt Failed example: print system(buildout), Expected: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory mystuff Got: Develop: '/sample-buildout/recipes' Installing data-dir. data-dir: Creating directory mystuff Regards Roger Ineichen _____________________________ END OF MESSAGE
-----Ursprüngliche Nachricht----- Von: zope-dev-bounces@zope.org [mailto:zope-dev-bounces@zope.org] Im Auftrag von Balazs Ree Gesendet: Freitag, 24. April 2009 13:39 An: zope-dev@zope.org Betreff: Re: [Zope-dev] zc.buildout broken
On Fri, 24 Apr 2009 13:10:30 +0200, Marius Gedminas wrote:
On Fri, Apr 24, 2009 at 05:56:45AM +0200, Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
It is always interesting to see the failures, but attaching large log files to emails is not very polite.
True for large files, but a traceback is not that large _imo_. Depends on your connection of course.
Also, we are on a development list, so if somewhere, then here tracebacks are on topic.
Solution: use a pastebin.
I disagree: pastebin is good for linking from irc, but when I come back to the archive I would like to see the details even when the pastebin entry is gone.
-- Balazs Ree
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
On 2009-04-24, Roger Ineichen <dev@projekt01.ch> wrote:
I think there are different things wrong. The first error looks like a difference in linux and windows output: ---------------------------------------------------------------------- File "d:\eggdev\source\zc\zc.buildout\trunk\src\zc\buildout\buildout.txt", line 55, in buildout.txt Failed example: ls(sample_buildout, 'eggs') Expected: setuptools.egg - zc.buildout.egg Got: - setuptools.egg-link - zc.buildout.egg
Actually, this very same difference is what I'm getting on OSX. So there's some deeper problem here. I get it with both python 2.4 and 2.5, btw. Perhaps the way setuptools is installed in our python environment? When testing with python2.4, my bin/buildout looks like this: ----- #!/opt/local/Library/Frameworks/Python.framework/Versions/2.4/Resources/Python.app/Contents/MacOS/Python import sys sys.path[0:0] = [ '/Users/reinout/svn/zc.buildout/src', '/Users/reinout/.buildout/eggs/zope.testing-3.7.3-py2.4.egg', '/Users/reinout/.buildout/eggs/zope.interface-3.5.1-py2.4-macosx-10.5-i386.egg', '/opt/local/lib/python2.4/site-packages', ] import zc.buildout.buildout if __name__ == '__main__': zc.buildout.buildout.main() ------ And my bin/test: ------ #!/opt/local/Library/Frameworks/Python.framework/Versions/2.4/Resources/Python.app/Contents/MacOS/Python import sys sys.path[0:0] = [ '/Users/reinout/svn/zc.buildout/src', '/Users/reinout/svn/zc.buildout/zc.recipe.egg_/src', '/Users/reinout/.buildout/eggs/zope.testing-3.7.3-py2.4.egg', '/Users/reinout/.buildout/eggs/zope.interface-3.5.1-py2.4-macosx-10.5-i386.egg', '/opt/local/lib/python2.4/site-packages', ] import os sys.argv[0] = os.path.abspath(sys.argv[0]) os.chdir('/Users/reinout/svn/zc.buildout/parts/test') import zope.testing.testrunner if __name__ == '__main__': zope.testing.testrunner.run([ '--test-path', '/Users/reinout/svn/zc.buildout/src', '--test-path', '/Users/reinout/svn/zc.buildout/zc.recipe.egg_/src', ]) ----- Does that give a hint? Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets
On 2009-04-24, Roger Ineichen <dev@projekt01.ch> wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
I have 9 failures and 1 error on OSX. Most of them have to do with there not being a setuptools egg, but a setuptools develop egg, for example: File "/Users/reinout/svn/zc.buildout/src/zc/buildout/unzip.txt", line 18, in unzip.txt Failed example: ls('eggs') Expected: - demo-0.4c1-pyN.N.egg - demoneeded-1.2c1-pyN.N.egg setuptools.egg - zc.buildout.egg-link Got: - demo-0.4c1-pyN.N.egg - demoneeded-1.2c1-pyN.N.egg - setuptools.egg-link - zc.buildout.egg-link I got some other warnings too: /opt/local/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/zipfile.py:7: RuntimeWarning: Python C API version mismatch for module zlib: This Python has API version 1012, module zlib has version 1013. I'm running the tests with python2.5, so a python2.4 error looks weird to me. Does zc.buildout test itself with multiple python versions? Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets
On 2009-04-24, Reinout van Rees <reinout@vanrees.org> wrote:
I have 9 failures and 1 error on OSX. Most of them have to do with there not being a setuptools egg, but a setuptools develop egg, for example:
Reminded by the talk about posting tracebacks: here's mine :-) http://reinout.vanrees.org/download/buildout_2009-04-24.txt Reinout -- Reinout van Rees - reinout@vanrees.org - http://reinout.vanrees.org Software developer at http://www.thehealthagency.com "Military engineers build missiles. Civil engineers build targets
On Apr 23, 2009, at 11:56 PM, Roger Ineichen wrote:
Hi everybody
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
You should expect trunk failures on Windows. Most people who contribute to buildout don't run tests on Windows. Windows tests should always be run and made to pass before making a release. I do. I get the 50 failures with Python 2.4. (BTW, it would help if you reported the Python version used.) Most or all of these are spurious and due to actual output lines having carriage returns at the ends. (I assume this is a side-effect of a recent change to using subprocess.) It should be easy to address this by adding a renormalizer. I'll get to this at some point, if someone doesn't beat me to it. Jim -- Jim Fulton Zope Corporation
On Fri, Apr 24, 2009 at 05:56, Roger Ineichen <dev@projekt01.ch> wrote:
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
Do you want a buildbot for zc.buildout? (py2.4, py2.5, py2.6 on linux 32&64, sorry) -- Sebastien Douche <sdouche@gmail.com>
On Fri, Apr 24, 2009 at 16:28, Jim Fulton <jim@zope.com> wrote:
Do you want a buildbot for zc.buildout? (py2.4, py2.5, py2.6 on linux 32&64, sorry)
+1
Done: http://misc.buildbot.securactive.org/waterfall (sorry, 32 bit slave is down) -- Sebastien Douche <sdouche@gmail.com>
Hi Sebastian
Betreff: Re: [Zope-dev] zc.buildout broken
On Fri, Apr 24, 2009 at 05:56, Roger Ineichen <dev@projekt01.ch> wrote:
Ran 367 tests with 50 failures and 1 errors in 8 minutes 14.891 seconds.
The latest trunk of zc.buildout is completly broken. At least on windows. Can someone check this on linux?
Do you want a buildbot for zc.buildout? (py2.4, py2.5, py2.6 on linux 32&64, sorry)
Yeah, whould be great! Regards Roger Ineichen
-- Sebastien Douche <sdouche@gmail.com>
participants (8)
-
Balazs Ree -
Chris Withers -
Jim Fulton -
Marius Gedminas -
Reinout van Rees -
Roger Ineichen -
Sebastien Douche -
Tres Seaver