1c63bb6130
Sort fan out results before comparison in test
2022-04-12 19:49:36 -04:00
9c27858aaf
WIP prints to debug frickin windows
2022-04-12 16:48:50 -04:00
fa354ffe2b
Handle not all values pulled case
2022-04-12 15:51:06 -04:00
333fad8819
Facepalm: join nursery first to avoid channel-closed-too-early
2022-04-12 15:06:35 -04:00
90593611bb
Add test for `LinkedTaskChannel.subscribe()` fanout feature
2022-04-12 15:06:35 -04:00
13c8300226
Add a sub-actor managed service nursery test scenario
2022-04-12 11:42:44 -04:00
9a2de90de6
Add mid stream echoserver "bail" cases
2021-12-17 09:38:04 -05:00
2b9b29eb71
Add an asyncio echo server test
2021-12-17 09:38:04 -05:00
c4b3bb354e
Port tests to handle our new `asyncio` cancelled type
2021-12-17 09:38:04 -05:00
ad2567dd73
Add first set of interloop streaming tests
2021-12-17 09:38:04 -05:00
d27ddb7bbb
Add a basic `open_channel_from()` streaming test
2021-12-17 09:38:04 -05:00
e815f766f6
Add a cancelled-from-remote-trio-task case
2021-12-17 09:38:04 -05:00
c19123b588
Add trio-cancels-anursery-cancels-aio test
2021-12-17 09:38:04 -05:00
04c0eda69d
Add an `asyncio`-internal cancel test
...
Verify that if the `asyncio` side task cancels (itself) that we raise
that `asyncio.CancelledError` on the `trio` side. In the case where
`trio` initiated the cancel whether or not the `asyncio` side ended up
raising `CancelledError` doesn't really matter to us as long as the far
task did indeed terminate.
2021-12-17 09:38:04 -05:00
56357242e9
Add a `Portal.cancel_actor()` test
2021-12-17 09:38:04 -05:00
299e4192b0
Plan asyncio test set
2021-12-17 09:38:04 -05:00
340effae11
Add initial infected asyncio error propagation test
2021-12-17 09:38:01 -05:00
Tyler Goodlet