forked from goodboy/tractor
268bd0d8ec
Finally this reproduces the issue as it (originally?) exhibited inside `piker` where the `Actor.lifetime_stack` wasn't closed in cases where during `infected_aio`-actor cancellation/shutdown `trio` side tasks which are doing shielded (teardown) work are NOT being watched/waited on from the `aio_main()` task-closure inside `run_as_asyncio_guest()`! This is then the root cause of the guest-run being abandoned since if our `aio_main()` task-closure doesn't know it should allow the run to finish, it's going to call `loop.close()` eventually resulting in the `GeneratorExit` thrown into `trio._core._run.unrolled_run()`.. So, this extends the `test_sigint_closes_lifetime_stack()` suite to include cases for such shielded `trio`-task ops: - add a new `trio_side_is_shielded: bool` which will toggle whether to add a shielded 0.5s `trio.sleep()` loop to `manage_file()` which should outlive the `asyncio` event-loop shutdown sequence and result in an abandoned guest-run and thus a leaked file. - parametrize the existing suite with this case resulting in a total 16 test set B) This patch demonstrates the problem with our `aio_main()` task-closure impl via the now 4 failing tests, a fix is coming in a follow up commit! |
||
|---|---|---|
| .. | ||
| conftest.py | ||
| test_2way.py | ||
| test_advanced_faults.py | ||
| test_advanced_streaming.py | ||
| test_cancellation.py | ||
| test_caps_based_msging.py | ||
| test_child_manages_service_nursery.py | ||
| test_clustering.py | ||
| test_context_stream_semantics.py | ||
| test_debugger.py | ||
| test_discovery.py | ||
| test_docs_examples.py | ||
| test_infected_asyncio.py | ||
| test_inter_peer_cancellation.py | ||
| test_legacy_one_way_streaming.py | ||
| test_local.py | ||
| test_multi_program.py | ||
| test_pldrx_limiting.py | ||
| test_pubsub.py | ||
| test_resource_cache.py | ||
| test_rpc.py | ||
| test_runtime.py | ||
| test_shm.py | ||
| test_spawning.py | ||
| test_task_broadcasting.py | ||
| test_trioisms.py | ||