Tyler Goodlet ecced3d09a Allow choosing the spawn backend per test session ... 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...		2020-01-26 21:36:08 -05:00
..
conftest.py	Allow choosing the spawn backend per test session	2020-01-26 21:36:08 -05:00
test_cancellation.py	Allow choosing the spawn backend per test session	2020-01-26 21:36:08 -05:00
test_discovery.py	Run first example test under both start methods	2019-10-30 00:31:28 -04:00
test_local.py	Verify subs topics at each step	2019-01-23 22:35:04 -05:00
test_multi_program.py	Check for proper SIGINT return code	2019-10-15 23:22:48 -04:00
test_pubsub.py	Add back line that breaks with async gens	2019-02-15 22:10:55 -05:00
test_rpc.py	Allow choosing the spawn backend per test session	2020-01-26 21:36:08 -05:00
test_spawning.py	Add subactor loglevel propagation test	2019-03-23 23:27:32 -04:00
test_streaming.py	Slight slowdown on windows / py3.8?	2019-10-16 11:02:18 -04:00