27 Commits (673aeef4e9f3fedec61bbca09924e54c08b0da8e)

Author	SHA1	Message	Date
Tyler Goodlet	a934eb063c	Factor `repodir()` helper into conftest.py	2020-10-13 14:49:31 -04:00
Guillermo Rodriguez	c993e36e95	Simplified CI detection	2020-09-03 09:44:24 -03:00
Guillermo Rodriguez	03e5852acf	Added some missing CI integration pieces	2020-09-02 13:19:42 -03:00
Tyler Goodlet	1ae0efb033	Make rpc_module_paths a list	2020-08-13 11:53:45 -04:00
Tyler Goodlet	7f74182a8a	Never allow more then info logging in daemon; causes blocking	2020-08-08 15:15:43 -04:00
Tyler Goodlet	2ccaa94c60	Move daemon fixture up to conftest	2020-08-03 15:39:54 -04:00
Tyler Goodlet	5a27065a10	Finally tame the super flaky tests ... - ease up on first stream test run deadline - skip streaming tests in CI for mp backend, period - give up on > 1 depth nested spawning with mp - completely give up on slow spawning on windows	2020-07-26 22:53:40 -04:00
Tyler Goodlet	dddbeb0e71	Run Windows on trio and mp backends ... The new pure trio spawning backend uses `subprocess` internally which is also supported on windows so let's run it in CI.	2020-07-25 13:41:48 -04:00
Guillermo Rodriguez	56463a08df	First attempt at removing trip & updating hazmat -> lowlevel	2020-07-24 17:08:52 -04:00
Tyler Goodlet	5fd38d4618	Force `mp` backend if option is blank?	2020-01-26 23:16:43 -05:00
Tyler Goodlet	b4cb7439a1	Drop useless fork error branch	2020-01-26 22:46:48 -05:00
Tyler Goodlet	7c1bc1fce4	Make windows job names explicit	2020-01-26 22:17:38 -05:00
Tyler Goodlet	e18fec9b17	Always force mp backend on Windows	2020-01-26 22:09:06 -05:00
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	783fe53b06	Don't mix trip with multiprocessing for now ... It seems that mixing the two backends in the test suite results in hangs due to lingering forkservers and resource managers from `multiprocessing`? Likely we'll need either 2 separate CI runs to work or someway to be sure that these lingering servers are killed in between tests.	2020-01-24 00:55:40 -05:00
Tyler Goodlet	bc259b7eab	Use trip as default in all tests for now	2020-01-24 00:54:19 -05:00
Tyler Goodlet	44996fe328	Add trip to start_method parametrizations	2020-01-23 01:16:10 -05:00
Tyler Goodlet	97df927714	Run first example test under both start methods	2019-10-30 00:31:28 -04:00
Christian López Barrón	efffca371a	pytest_generate_tests remove `fork` only if it's in list	2019-03-13 21:32:45 +11:00
Tyler Goodlet	b70f4eafcb	Flip tests to use `start_method` kwarg	2019-03-08 20:06:16 -05:00
Tyler Goodlet	483ae42a46	Add a `spawn_method` dynamic fixture	2019-03-06 00:36:37 -05:00
Tyler Goodlet	512a2f25a2	Expose `tractor_test` in the same way as `trio`	2018-11-26 11:26:04 -05:00
Tyler Goodlet	0879150399	Move `tractor_test` to new module	2018-11-26 11:20:53 -05:00
Tyler Goodlet	d12136d44d	Add some mult-program tests ... Run the arbiter-actor in a separate program and do some basic tests to make sure everything works - particularly, registration and cancellation.	2018-09-08 09:44:29 -04:00
Tyler Goodlet	e4ef973be9	Add discovery testing ... Add a new test to verify actors register with their `.uid` tuple as per #7. Break off relevant "discovery" tests into a new test module.	2018-08-07 14:30:25 -04:00
Tyler Goodlet	64cbb922dc	Reorg everything into private modules	2018-07-14 16:09:05 -04:00
Tyler Goodlet	a26d6f831f	Add loglevel setting to test suite	2018-07-11 22:24:19 -04:00