forked from goodboy/tractor
ecced3d09a
Add a `--spawn-backend` option which can be set to one of {'mp', 'trio_run_in_process'} which will either run the test suite using the `multiprocessing` or `trio-run-in-process` backend respectively. Currently trying to run both in the same session can result in hangs seemingly due to a lack of cleanup of forkservers / resource trackers from `multiprocessing` which cause broken pipe errors on occasion (no idea on the details). For `test_cancellation.py::test_nested_multierrors`, use less nesting when mp is used since it breaks if we push it too hard with the whole recursive subprocess spawning thing... |
||
---|---|---|
.. | ||
testing | ||
__init__.py | ||
_actor.py | ||
_discovery.py | ||
_exceptions.py | ||
_forkserver_override.py | ||
_ipc.py | ||
_portal.py | ||
_spawn.py | ||
_state.py | ||
_streaming.py | ||
_trionics.py | ||
log.py | ||
msg.py |