I'm seeing a failure in the tests for the zopeskel recipe template that started 
popping up when I tried testing my new templer.core package outside my regular 
build environment.

It turns out that pinning zc.buildout to version 1.4.3 solves the problem, so 
I'm pretty certain that whatever is causing it arises due to changes in the 1.5 
series of zc.buildout.

The failure doesn't crop up because of failures in the recipe.txt doctest, but 
rather because of problems when that test attempts to run the tests in the 
template recipe it has created (took me a while to wrap my head around that 
one).  If i pin zc.buildout to 1.4.3 or less in the setup.py for the generated 
buildout recipe, the failure disappears.  

I'm pretty sure that pinning all our templates to a version of zc.buildout that 
is now a year old isn't such a hot idea, but it did get me back to passing 
tests.  I'm hopeful that someone on this list might be able to help hunt down 
the problem and get us a solution that is better than mine.  

Here's what I get when I generate a recipe using the recipe template and then 
try to run the tests for it in a fresh virtualenv:

(killme.env)trurl:my.nifty.recipe cewing$ python setup.py test
running test
Checking .pth file support in .
/Users/cewing/virtualenvs/killme.env/bin/python -E -c pass
Searching for zc.buildout
Reading http://pypi.python.org/simple/zc.buildout/
Reading http://buildout.org
Best match: zc.buildout 1.5.2
Downloading 
http://pypi.python.org/packages/source/z/zc.buildout/zc.buildout-1.5.2.tar.gz#md5=87f7b3f8d13926c806242fd5f6fe36f7
Processing zc.buildout-1.5.2.tar.gz
Running zc.buildout-1.5.2/setup.py -q bdist_egg --dist-dir 
/var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/easy_install-53M4a9/zc.buildout-1.5.2/egg-dist-tmp-WrPbTV

Installed 
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/zc.buildout-1.5.2-py2.6.egg
Searching for zope.testing
Reading http://pypi.python.org/simple/zope.testing/
Reading http://svn.zope.org/zope.testing
Best match: zope.testing 3.10.2
Downloading 
http://pypi.python.org/packages/source/z/zope.testing/zope.testing-3.10.2.tar.gz#md5=35fc3139992a92a4db13653167fc7be9
Processing zope.testing-3.10.2.tar.gz
Running zope.testing-3.10.2/setup.py -q bdist_egg --dist-dir 
/var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/easy_install-4eTb4q/zope.testing-3.10.2/egg-dist-tmp-SEm1iZ
warning: no files found matching '*.test' under directory 'src'
warning: no files found matching 'sampletests' under directory 'src'

Installed 
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/zope.testing-3.10.2-py2.6.egg
Searching for zope.interface
Reading http://pypi.python.org/simple/zope.interface/
Best match: zope.interface 3.6.1
Downloading 
http://pypi.python.org/packages/source/z/zope.interface/zope.interface-3.6.1.tar.gz#md5=7a895181b8d10be4a7e9a3afa13cd3be
Processing zope.interface-3.6.1.tar.gz
Running zope.interface-3.6.1/setup.py -q bdist_egg --dist-dir 
/var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/easy_install-Ll1jZC/zope.interface-3.6.1/egg-dist-tmp-80c_9g

Installed 
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/zope.interface-3.6.1-py2.6-macosx-10.6-i386.egg
Searching for zope.exceptions
Reading http://pypi.python.org/simple/zope.exceptions/
Reading http://svn.zope.org/zope.exceptions
Best match: zope.exceptions 3.6.1
Downloading 
http://pypi.python.org/packages/source/z/zope.exceptions/zope.exceptions-3.6.1.zip#md5=b735a62e1ef16e746764b4938a4d7926
Processing zope.exceptions-3.6.1.zip
Running zope.exceptions-3.6.1/setup.py -q bdist_egg --dist-dir 
/var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/easy_install-SFXq6_/zope.exceptions-3.6.1/egg-dist-tmp-gRyRWc

Installed 
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/zope.exceptions-3.6.1-py2.6.egg
running egg_info
writing requirements to my.nifty.recipe.egg-info/requires.txt
writing my.nifty.recipe.egg-info/PKG-INFO
writing namespace_packages to my.nifty.recipe.egg-info/namespace_packages.txt
writing top-level names to my.nifty.recipe.egg-info/top_level.txt
writing dependency_links to my.nifty.recipe.egg-info/dependency_links.txt
writing entry points to my.nifty.recipe.egg-info/entry_points.txt
reading manifest file 'my.nifty.recipe.egg-info/SOURCES.txt'
writing manifest file 'my.nifty.recipe.egg-info/SOURCES.txt'
running build_ext
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/zope.testing-3.10.2-py2.6.egg/zope/testing/doctest/__init__.py:104:
 DeprecationWarning: zope.testing.exceptions is deprecated in favour of 
zope.testrunner.exceptions
  from zope.testing.exceptions import DocTestFailureException
/Users/cewing/virtualenvs/killme.env/my.nifty.recipe/my/nifty/recipe/tests/test_docs.py:11:
 DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python 
standard library doctest module
  from zope.testing import doctest, renormalizing
Doctest: README.txt ... Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/distribute/
Couldn't retrieve index page for 'distribute'
Scanning index of all packages (this may take a while)
Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/
Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/zc.buildout/
Couldn't retrieve index page for 'zc.buildout'
ok

----------------------------------------------------------------------
Ran 1 test in 1.205s

OK


As you can see, the test passes, but instead of the last line of output from 
the test run reading:

'Doctest: README.txt ... ok' 

as the recipe doctest expects, it reads instead:

Doctest: README.txt ... Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/distribute/
Couldn't retrieve index page for 'distribute'
Scanning index of all packages (this may take a while)
Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/
Reading 
file:///var/folders/Pe/Pec3chMwETiCgRaTDhGGwE+++TM/-Tmp-/tmpteOlhFbuildouttests/zc.buildout/
Couldn't retrieve index page for 'zc.buildout'
ok

There's a bunch of extra cruft that comes between the declaration that the test 
is running and the 'ok' that means it has passed.  This cruft does not appear 
when running the tests with zc.buildout pinned to 1.4.3

As I said above, I'm hopeful that someone can step up and help me solve this 
one.  I've got a working test suite by pinning zc.buildout to 1.4.3, but this 
is not the right way to do it, and i"m hoping one of you can help.

Thanks in advance,

c


********************************
Cris Ewing
Webmaster, Lead Developer
Department of Radiology Web Services
University of Washington
School of Medicine
Work Phone: (206) 616-1288
Cell Phone: (206) 708-9083
E-mail: cew...@u.washington.edu
Web: http://www.rad.washington.edu
*******************************

_______________________________________________
ZopeSkel mailing list
ZopeSkel@lists.plone.org
http://lists.plone.org/mailman/listinfo/zopeskel

Reply via email to