New issue 289: buildout + py.test + xdist
https://bitbucket.org/hpk42/pytest/issue/289/buildout-pytest-xdist
Tom Willis:
we have an appengine project that we unit test with py.test and I would love to
get it running things in parallel if possible. I hate to call this a bug,
because I just don't know, but the tracker won't let me assign anything closer
to appropriate.
After installing py.test and xdist in buildout...
(development *) twillis@hello-kitty:~/projects/buttercup_dev$ ./bin/py.test -n8
src/hydrant-app/tests/integration/
=====================================================================================================================================================
test session starts
=====================================================================================================================================================
platform linux2 -- Python 2.7.3 -- pytest-2.3.4
plugins: cov, xdist
gw0 C / gw1 C / gw2 C / gw3 C / gw4 C / gw5 C / gw6 C / gw7 C[gw0] node down:
Traceback (most recent call last):
File
"/home/twillis/.buildout/eggs/execnet-1.1-py2.7.egg/execnet/gateway_base.py",
line 800, in executetask
do_exec(co, loc)
File "<string>", line 1, in do_exec
File "", line 134, in <module>
ImportError: No module named py
if I instead install pytest and pytest-xdist in my system python distribution I
have to add ./ext to PYTHON_PATH which is a place where all libs are symlinked
to make it easier for my editor to find the source.
(development *) twillis@hello-kitty:~/projects/buttercup_dev$
PYTHON_PATH=./ext:$PYTHON_PATH py.test -n8
src/hydrant-app/tests/integration/test_account.py
=====================================================================================================================================================
test session starts
=====================================================================================================================================================
platform linux2 -- Python 2.7.3 -- pytest-2.3.4
plugins: xdist, cov
gw0 [0] / gw1 [0] / gw2 [0] / gw3 [0] / gw4 [0] / gw5 [0] / gw6 [0] / gw7 [0]
scheduling tests via LoadScheduling
======================================================================================================================================================
in 0.48 seconds
=======================================================================================================================================================
so no error, but my tests don't run.
attached is the py.test script generated by buildout which has all the paths
our buildout environment requires.
any ideas?
--
This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.
_______________________________________________
pytest-commit mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pytest-commit