I’m running py.test on Linux in the context of a module that makes heavy usage of multiprocessing. Exceptions in child processes are not detected as an error. Example test file pytest_mp_test.py:
import multiprocessing
def test_mp():
p = multiprocessing.Process(target=child)
p.start()
p.join()
def child():
assert False
Execution:
$ py.test pytest_mp_test.py
================================== test session starts ===================================
platform linux2 -- Python 2.7.3 -- pytest-2.3.3
plugins: cov
collected 1 items
pytest_mp_test.py .
================================ 1 passed in 0.04 seconds ================================
No error detected. The exception is printed when invoked with -s:
$ py.test -s pytest_mp_test.py
================================== test session starts ===================================
platform linux2 -- Python 2.7.3 -- pytest-2.3.3
plugins: cov
collected 1 items
pytest_mp_test.py Process Process-1:
Traceback (most recent call last):
File "/apps11/bioinfp/Python-2.7.3/lib/python2.7/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/apps11/bioinfp/Python-2.7.3/lib/python2.7/multiprocessing/process.py", line 114, in run
self._target(*self._args, **self._kwargs)
File "/home/bioinfp/jang/hobbyproggorn/gevent-messagepipe/gevent-messagepipe/pytest_mp_test.py", line 9, in child
assert False
AssertionError: assert False
.
================================ 1 passed in 0.04 seconds ================================
When I manually review the test log, I realize when there is a problem. However, I am wondering if there a neat way to automate exception detection in a child with py.test.
Must I verify the child’s exit code in the parent? Is this the only way?
After some further consideration, I think that just catching the expected exception in the child and checking for the child’s exit state is a very clean and reliable solution, that does not add an additional IPC component to the tests. Example code:
Execution: