Skip to content

Use trio from pypi #139

Use trio from pypi

Use trio from pypi #139

Triggered via push November 13, 2023 14:31
Status Failure
Total duration 58s
Artifacts

unit-test.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

37 errors and 10 warnings
build (3.11, (none))
Process completed with exit code 1.
build (3.12, (none))
Process completed with exit code 1.
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorStartedState.paused] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_can_pause_and_resume_after_start[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.degraded] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.unhealthy] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorState.crashed] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_id_is_set[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actors.py#L116
test_actor_id_is_a_uuid_by_default[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actor_resources.py#L116
test_resource_unavailable[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actor_resources.py#L116
test_resource_accessor[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (none)): tests/actors/test_actor_resources.py#L116
test_acquire_resource_within_specified_timeout[trio-sync resource] ModuleNotFoundError: No module named 'trio'
build (3.12, (diagrams))
The operation was canceled.
build (3.10, (diagrams))
The operation was canceled.
build (3.10, (none))
The operation was canceled.
build (3.9, (none))
The operation was canceled.
build (3.11, (diagrams))
The operation was canceled.
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.unhealthy] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.healthy] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorState.crashed] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_id_is_set[trio] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_id_is_a_uuid_by_default[trio] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.degraded] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actor_resources.py#L116
test_acquire_async_resource_timed_out[trio] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorStartedState.paused] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.healthy] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actor_resources.py#L116
test_acquire_resource[trio-sync resource] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_id_is_a_uuid_by_default[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_id_is_set[trio] ModuleNotFoundError: No module named 'trio'
build (3.9, (diagrams)): tests/actors/test_actors.py#L49
test_actor_can_transition_back_to_starting_after_stopped[asyncio] RuntimeError: Attempted to exit cancel scope in a different task than it was entered in
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.unhealthy] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorState.crashed] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_transition_back_to_starting_after_stopped[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_pause_and_resume_after_start[trio] ModuleNotFoundError: No module named 'trio'
build (3.8, (diagrams)): tests/actors/test_actors.py#L49
test_actor_can_transition_back_to_starting_after_stopped[asyncio+uvloop] RuntimeError: Attempted to exit cancel scope in a different task than it was entered in
build (3.8, (diagrams)): tests/actors/test_actors.py#L49
test_actor_can_transition_back_to_starting_after_stopped[asyncio] RuntimeError: Attempted to exit cancel scope in a different task than it was entered in
build (3.8, (diagrams)): tests/actors/test_actors.py#L116
test_actor_can_restart[trio-ActorRunningState.degraded] ModuleNotFoundError: No module named 'trio'
build (3.11, (none))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.12, (none))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.8, (none))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.12, (diagrams))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10, (diagrams))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10, (none))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9, (none))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.11, (diagrams))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9, (diagrams))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.8, (diagrams))
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/