Skip to content

Do I also need to not fail fast? #56

Do I also need to not fail fast?

Do I also need to not fail fast? #56

Triggered via push July 3, 2024 20:27
Status Cancelled
Total duration 2m 3s
Artifacts 1

ci.yml

on: push
Matrix: sync
Matrix: build-docs
Matrix: fawltydeps
Matrix: pyright
Matrix: ruff
Matrix: test
Matrix: deploy-docs
Matrix: lock
Fit to window
Zoom out
Zoom in

Annotations

18 errors
test (macos-13, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (macos-13, 3.11)
The operation was canceled.
test (windows-2022, 3.12)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (windows-2022, 3.12)
The operation was canceled.
test (windows-2022, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (windows-2022, 3.11)
The operation was canceled.
ruff (ubuntu-22.04, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
ruff (ubuntu-22.04, 3.11)
The operation was canceled.
build-docs (ubuntu-22.04, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
build-docs (ubuntu-22.04, 3.11)
The operation was canceled.
pyright (ubuntu-22.04, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
pyright (ubuntu-22.04, 3.11)
The operation was canceled.
test (ubuntu-22.04, 3.12)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (ubuntu-22.04, 3.12)
The operation was canceled.
test (ubuntu-22.04, 3.11)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (ubuntu-22.04, 3.11)
The operation was canceled.
test (macos-13, 3.12)
Canceling since a higher priority waiting request for 'ci-refs/heads/main' exists
test (macos-13, 3.12)
The operation was canceled.

Artifacts

Produced during runtime
Name Size
lock Expired
6.17 KB