Skip to content

Fix TaskStatus.started() being a no-op when in an effectively cancelled scope #5233

Fix TaskStatus.started() being a no-op when in an effectively cancelled scope

Fix TaskStatus.started() being a no-op when in an effectively cancelled scope #5233

Triggered via pull request January 9, 2024 18:16
Status Failure
Total duration 42m 28s
Artifacts

ci.yml

on: pull_request
Matrix: macOS
Matrix: Ubuntu
Matrix: Windows
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Ubuntu (3.11)
Process completed with exit code 1.
Ubuntu (3.12-dev)
Process completed with exit code 1.
check
Process completed with exit code 1.