Skip to content

Integrate aws-ip-ranges as workspace crate #26793

Integrate aws-ip-ranges as workspace crate

Integrate aws-ip-ranges as workspace crate #26793

Triggered via pull request October 28, 2025 18:35
Status Cancelled
Total duration 2m 26s
Artifacts

ci.yml

on: pull_request
Changed Files
12s
Changed Files
Frontend / Percy Nonce
3s
Frontend / Percy Nonce
Backend / Lint
2m 7s
Backend / Lint
Backend / dependencies
28s
Backend / dependencies
Backend / Test
2m 8s
Backend / Test
Frontend / Lint
44s
Frontend / Lint
Frontend / Test (@crates-io/msw)
54s
Frontend / Test (@crates-io/msw)
CI / Lint
17s
CI / Lint
Frontend / Test
1m 59s
Frontend / Test
Frontend / Test (playwright)
1m 58s
Frontend / Test (playwright)
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 1 warning
Backend / dependencies
Process completed with exit code 4.
Frontend / Lint
Process completed with exit code 1.
Backend / Lint
Canceling since a higher priority waiting request for ci-integrate-aws-ip-ranges-workspace exists
Backend / Lint
The operation was canceled.
Backend / Test
Canceling since a higher priority waiting request for ci-integrate-aws-ip-ranges-workspace exists
Backend / Test
The operation was canceled.
Frontend / Test (playwright)
Canceling since a higher priority waiting request for ci-integrate-aws-ip-ranges-workspace exists
Frontend / Test (playwright)
The operation was canceled.
Frontend / Test
Canceling since a higher priority waiting request for ci-integrate-aws-ip-ranges-workspace exists
Frontend / Test
The operation was canceled.
CI
Canceling since a higher priority waiting request for ci-integrate-aws-ip-ranges-workspace exists
CI / Lint
No file matched to [/home/runner/work/crates.io/crates.io/**/*requirements*.txt,/home/runner/work/crates.io/crates.io/**/*requirements*.in,/home/runner/work/crates.io/crates.io/**/*constraints*.txt,/home/runner/work/crates.io/crates.io/**/*constraints*.in,/home/runner/work/crates.io/crates.io/**/pyproject.toml,/home/runner/work/crates.io/crates.io/**/uv.lock,/home/runner/work/crates.io/crates.io/**/*.py.lock]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.