4 Commits (409ceefd6e3f662882724b8a6fbd2fd3cdf8f9ca)

Author	SHA1	Message	Date
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
Tyler Goodlet	e1a55a6f4f	Importing happens once locally now so expect a local error	2020-01-21 10:28:32 -05:00
Tyler Goodlet	d2f0537850	Add tests for import-time failures	2019-01-12 17:56:39 -05:00
Tyler Goodlet	fe4a39550d	Add remote module error handling tests	2019-01-01 16:12:34 -05:00