1b6ee2ecf6
Skip sync sleep test on windows
2020-10-13 15:26:46 -04:00
15edcc622d
Skip it on windows too
2020-10-13 15:13:46 -04:00
fd59f4ad16
On windows .spawn dne?
2020-10-13 14:56:26 -04:00
a934eb063c
Factor `repodir()` helper into conftest.py
2020-10-13 14:49:31 -04:00
a49deb46f1
Revert "Make tests a package (for relative imports)"
...
This reverts commit 1710b642a5
2020-10-13 14:42:16 -04:00
666966097a
Revert "Change to relative conftest.py imports"
...
This reverts commit 2b53c74b1c
2020-10-13 14:42:02 -04:00
ba52de79e1
Skip quad ex on local mp tests as well
2020-10-13 14:20:19 -04:00
24ef919334
Skip sync sleep test on mp backend
2020-10-13 14:16:20 -04:00
1710b642a5
Make tests a package (for relative imports)
2020-10-13 10:50:21 -04:00
a88a6ba7a3
Add pattern matching to test
2020-10-13 00:36:34 -04:00
0e344eead8
Add a "cancel arrives during a sync sleep in child" test
...
This appears to demonstrate the same bug found in #156 . It looks like
cancelling a subactor with a child, while that child is running sync code,
can result in the child never getting cancelled due to some strange
condition where the internal nurseries aren't being torn down as
expected when a `trio.Cancelled` is raised.
2020-10-12 23:25:22 -04:00
acb4cb0b2b
Add test showing issue with child in tty lock when cancelled
2020-10-07 06:08:31 -04:00
abf8bb2813
Add a deep nested error propagation test
2020-10-06 09:21:53 -04:00
2b53c74b1c
Change to relative conftest.py imports
2020-10-05 11:58:58 -04:00
371025947a
Add a multi-subactor test where the root errors
2020-10-05 11:58:58 -04:00
31c1a32d58
Add re-entrant root breakpoint test; demonstrates a bug..
2020-10-05 11:58:58 -04:00
e387e8b322
Add a multi-subactor test with nesting
2020-10-05 11:58:58 -04:00
73a32f7d9c
Add initial subactor debug tests
2020-10-05 11:58:58 -04:00
0a2a94fee0
Add initial root actor debugger tests
2020-10-05 11:58:58 -04:00
e7ee0fec34
Pass a copy of the expected exposed modules
2020-09-24 10:12:10 -04:00
5e3ce765dd
Drop mac support, will continue the experiment on another branch
2020-09-03 10:41:09 -03:00
ad68ff665f
Missing a platform.system() check
2020-09-03 09:57:04 -03:00
c993e36e95
Simplified CI detection
2020-09-03 09:44:24 -03:00
03e5852acf
Added some missing CI integration pieces
2020-09-02 13:19:42 -03:00
451170bb63
Pass explicit kwargs to new discovery test funcs
2020-08-13 13:26:08 -04:00
0c8dcd0ec5
Use allocated arbiter port in local reg test
2020-08-13 11:54:37 -04:00
1ae0efb033
Make rpc_module_paths a list
2020-08-13 11:53:45 -04:00
acd5b80f4c
Add close channel test with remote arbiter
2020-08-08 15:17:04 -04:00
c821690834
Actor cancellation is now more latent; loosen timeing
2020-08-08 15:16:10 -04:00
7f74182a8a
Never allow more then info logging in daemon; causes blocking
2020-08-08 15:15:43 -04:00
3a868fec30
Cancel root nursery to trigger failure
...
The real issue is if the root nursery gets cancelled prior to
de-registration with the arbiter. This doesn't seem easy to
reproduce by side effect of a KBI however that is how it was
discovered in practise.
2020-08-07 11:34:17 -04:00
d2d8860dad
Add test for dereg failure on manual stream close
...
There was code from the last de-registration fix PR that I had commented
(to do with shielding arbiter dereg steps in `Actor._async_main()`) because
the block didn't seem to make a difference under infinite streaming
tests. Turns out it **for sure** is needed under certain conditions (likely
if the actor's root nursery is cancelled prior to actor nursery exit).
This was an attempt to simulate the failure mode if you manually close the
stream **before** cancelling the containing **actor**.
More tests to come I guess.
2020-08-07 09:16:01 -04:00
a5279f80a7
Actually reproduce the de-registration problem
...
This truly reproduces #141 . It turns out the problem only occurs when
we're cancelled in the middle of consuming "infinite streams".
Good news is this tests a lot of edge cases :)
2020-08-03 18:28:09 -04:00
699bfd1857
Run unreg on cancel tests with remote arbiter as well
2020-08-03 15:41:41 -04:00
2ccaa94c60
Move daemon fixture up to conftest
2020-08-03 15:39:54 -04:00
0d9483376d
Test cancel with SIGINT on non-windows as well
2020-08-03 13:01:56 -04:00
cd2d8c217a
Test that subactors deregister on cancel
2020-08-03 12:53:03 -04:00
da56d0f043
Add slight delays to SIGINT tests on mp
2020-07-29 13:27:15 -04:00
8f17c89cf9
Skip **every** quad test for mp on ci
2020-07-29 10:26:19 -04:00
5715fd4599
Skip streaming tests
2020-07-27 12:20:46 -04:00
e8a38e4d15
Fix cancelled type handling
2020-07-27 11:15:05 -04:00
3c7ec72f8e
Fix SIGINT test names
2020-07-26 23:37:44 -04:00
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
891edbab5f
Run the trio spawner in nested tests
2020-07-25 18:19:17 -04:00
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
a215df8dfc
Add true ctrl-c tests using an out-of-band SIGINT
...
Verify ctrl-c, as a user would trigger it, properly cancels the actor
tree. This was an issue with `trio-run-in-process` that clearly wasn't
being handled correctly but for sure is now with the plain old
`trio` process spawner.
Resolves #115
2020-07-24 17:08:52 -04:00
4de75c3a9d
Test cancel via api and keyboard interrupt
...
An initial attempt to discover an issue with trio-run-inprocess.
This is a good test to have regardless.
2020-07-24 17:08:52 -04:00
5adf2f3b0c
Add logging to some cancel tests
2020-07-24 17:08:52 -04:00
56463a08df
First attempt at removing trip & updating hazmat -> lowlevel
2020-07-24 17:08:52 -04:00
d62610c44e
Search for guard and strip instead of hardcoding
2020-02-10 12:59:44 -05:00
Tyler Goodlet
Guillermo Rodriguez