Skip to content

Have cargo metadata and cargo fetch use the same cargo when building library packages #6723

Have cargo metadata and cargo fetch use the same cargo when building library packages

Have cargo metadata and cargo fetch use the same cargo when building library packages #6723

Triggered via pull request February 11, 2025 13:59
@smoeliussmoelius
synchronize #1519
same-cargo
Status Cancelled
Total duration 27m 40s
Artifacts

ci.yml

on: pull_request
maybe-expedite
3s
maybe-expedite
Matrix: test
all-checks
0s
all-checks
Fit to window
Zoom out
Zoom in

Annotations

11 errors
lint
Process completed with exit code 1.
test (ubuntu-latest, cargo-dylint-ci)
Process completed with exit code 101.
test (windows-latest, cargo-dylint-cargo-lib)
Canceling since a higher priority waiting request for 'ci-refs/pull/1519/merge' exists
test (windows-latest, cargo-dylint-cargo-lib)
The operation was canceled.
test (windows-latest, other)
Canceling since a higher priority waiting request for 'ci-refs/pull/1519/merge' exists
test (windows-latest, other)
The operation was canceled.
test (windows-latest, cargo-dylint)
Canceling since a higher priority waiting request for 'ci-refs/pull/1519/merge' exists
test (windows-latest, cargo-dylint)
The operation was canceled.
test (windows-latest, dylint_examples)
Canceling since a higher priority waiting request for 'ci-refs/pull/1519/merge' exists
test (windows-latest, dylint_examples)
The operation was canceled.
all-checks
Process completed with exit code 1.