e45251db56
Simplify to form submitted to njs
2022-04-12 13:05:26 -04:00
faf751acac
WIP reproduce deadlock issue during error from piker
2022-04-12 13:04:46 -04:00
13c8300226
Add a sub-actor managed service nursery test scenario
2022-04-12 11:42:44 -04:00
c5acc3b969
Pack tuple keys as . delim strs in registry tests
2022-02-15 08:48:07 -05:00
ffe88de53b
Better idea: start a `tractor.experimental` subpkg
2022-01-29 14:03:55 -05:00
9ab04b1f6b
One more increase for py3.10
2022-01-21 12:20:06 -05:00
b3ff4b7804
Increase some timeouts for windows
2022-01-21 12:20:06 -05:00
d65912e1ae
Increase kbi delay in remote cancel test
2021-12-17 09:38:04 -05: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
916e27eedc
Adjust cancelled test to expect raised overrun error
2021-12-16 19:59:10 -05:00
9650b010de
Add a test for the real issue: error overriding
...
The underlying issue is actually that a nested `Context` which was
cancelled was overriding the local error that triggered that secondary's
context's cancellation in the first place XD. This test catches that
case.
Relates to https://github.com/pikers/piker/issues/244
2021-12-16 19:59:10 -05:00
c38d0f826e
Add an unserializable value causes error before started test
2021-12-16 19:59:10 -05:00
21a9c47496
Parameterize over cache keying methods: kwargs and "key"
2021-12-16 18:02:03 -05:00
67dc0d014c
Add basic `maybe_open_context()` caching test
2021-12-16 18:02:03 -05:00
9b1d8bf7b0
Of course, increase the timeout for windows..
2021-12-16 18:02:03 -05:00
f617da6ff1
Add timeout around test and prints for guidance
2021-12-16 18:02:03 -05:00
4a0252baf2
Add task-cached stream test
2021-12-16 18:02:03 -05:00
1652716574
Add timeout to streaming test
2021-12-16 16:19:09 -05:00
79d63585b0
Add a multi-task fan out streaming test
...
This actually catches a lot of bugs to do with stream termination and
``MsgStream.subscribe()`` usage where the underlying stream closes from
the producer side. When this passes the broadcaster logic will have to
ensure non-lossy fan out semantics and closure tracking.
2021-12-16 16:16:23 -05:00
a38a983225
Increase debugger poll delay back to prior value
...
If we make it too fast a nursery with debug mode children can cancel
too fast and causes some test failures. It's likely not a huge deal
anyway since the purpose of this poll/check is for human interaction
and the current delay isn't really that noticeable.
Decrease log levels in the debug module to avoid console noise when in
use. Toss in some more detailed comments around the new debugger lock
points.
2021-12-10 11:54:27 -05:00
4f411d6926
Add a per actor debug mode test
2021-12-09 17:53:31 -05:00
95c52436e5
Adjust multi-actor debugger test
...
It turns out recent improvements have made the debugger too good
so we need to just terminate the continue loop in this test when
we finally see the "spawn error" crash out because the breakpoint
forever case will literally, continue forever XD
2021-12-07 16:46:03 -05:00
e51c0e17a2
Properly set console logging in test suite
2021-12-07 13:17:10 -05:00
205e254072
Make test suite use default log level
2021-12-07 13:13:40 -05:00
703dee8a59
Add stream open before started, detailed semantics comment
2021-12-07 09:48:35 -05:00
df59071747
Bleh cast to list for `msgpack`
2021-12-06 18:07:14 -05:00
efba5229fc
Move context-streaming operational tests into one mod
2021-12-06 16:45:44 -05:00
fd6f4574ce
Rename test mod
2021-12-06 16:38:27 -05:00
52a2b7a5ed
Bump windows timeout again
2021-12-06 16:32:23 -05:00
63ecae70c4
Add a basic no-errors-when-backpressure stream test
2021-12-06 16:32:23 -05:00
a79cdc7b44
Make cancel case expect multi-error
2021-12-06 16:32:23 -05:00
58805a0430
Slight delay to avoid flaky bcast race
2021-12-06 12:17:37 -05:00
142083d81b
Don't cancel the context on overrun cases
2021-12-06 11:54:21 -05:00
f3432bd8fb
Enable bp on clustering test
2021-12-05 20:02:55 -05:00
7b9d410c4d
Adjust remaining examples and tests for non-backpressure default
2021-12-05 19:52:09 -05:00
2b05ffcc23
Add context stream overrun tests
2021-12-05 19:50:39 -05:00
872b24aedd
Prove we've fixed #265
2021-12-03 14:49:55 -05:00
3f6099f161
Add a double started error checking test
2021-12-03 10:08:55 -05:00
568902a5a9
Add test for #265 : "msg sent before stream opened"
...
This always triggered the mentioned race condition.
We need to figure out the best approach to avoid this case.
2021-12-03 10:08:55 -05:00
a29924f330
Don't assume exception order from nursery
2021-12-02 08:45:58 -05:00
Tyler Goodlet