summaryrefslogtreecommitdiff
path: root/functional_tests
diff options
context:
space:
mode:
authorJohn Szakmeister <john@szakmeister.net>2012-11-11 13:35:24 -0500
committerJohn Szakmeister <john@szakmeister.net>2012-11-11 13:35:24 -0500
commit51b567b381f11609eb0190a8fda34c91a2d1ab6f (patch)
tree2c088f21bfb97e08c27add296ea577a19229e540 /functional_tests
parentbe14c74d40aa2b36858a270d6513e8a0290d19ce (diff)
downloadnose-51b567b381f11609eb0190a8fda34c91a2d1ab6f.tar.gz
multiprocess: make test a little less racy
The other process can start up not long after the module setup and teardown is called. Add another ellipsis in to cover this case. Note: it's feasible that something could sneak in between the setup and teardown as well, but the failures with Travis haven't shown that to be occurring.
Diffstat (limited to 'functional_tests')
-rw-r--r--functional_tests/doc_tests/test_multiprocess/multiprocess.rst1
1 files changed, 1 insertions, 0 deletions
diff --git a/functional_tests/doc_tests/test_multiprocess/multiprocess.rst b/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
index d463ba0..ca966af 100644
--- a/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
+++ b/functional_tests/doc_tests/test_multiprocess/multiprocess.rst
@@ -223,6 +223,7 @@ Then we can run again and see the failures.
... plugins=[MultiProcess()]) #doctest: +ELLIPSIS
setup called
teardown called
+ ...
test_can_split....
...
FAILED (failures=...)