chore: sync public mirror from internal #386
Triggered via pull request
September 29, 2026 21:20
evalops-mirror[bot]
Status
Failure
Total duration
12m 23s
Artifacts
–
maestro-ci.yml
on: pull_request
protocol-contracts
13s
Matrix: rust-tests
lint
1m 14s
native-release
1m 30s
integration
1m 26s
scenario-replay
1m 18s
ci-contracts
11s
workflow-tooling
23s
supply-chain
3m 14s
jetbrains-plugin
1m 53s
linux-check
1m 32s
maestro-ci
4s
Annotations
11 errors and 4 warnings
|
scenario-replay
Process completed with exit code 101.
|
|
integration
Process completed with exit code 101.
|
|
rust-tests (1)
Process completed with exit code 101.
|
|
supply-chain
Process completed with exit code 1.
|
|
rust-tests (2)
Process completed with exit code 102.
|
|
rust-tests (3)
Process completed with exit code 102.
|
|
lint
Process completed with exit code 1.
|
|
linux-check
Process completed with exit code 2.
|
|
native-release
Process completed with exit code 101.
|
|
rust-tests (4)
Process completed with exit code 102.
|
|
maestro-ci
Process completed with exit code 1.
|
|
rust-tests (1)
install-action: cargo-nextest is supported but version 0.9.143 for 'x86_64_linux' is not supported (updating install-action might resolve this); fallback to cargo-binstall
|
|
rust-tests (2)
install-action: cargo-nextest is supported but version 0.9.143 for 'x86_64_linux' is not supported (updating install-action might resolve this); fallback to cargo-binstall
|
|
rust-tests (3)
install-action: cargo-nextest is supported but version 0.9.143 for 'x86_64_linux' is not supported (updating install-action might resolve this); fallback to cargo-binstall
|
|
rust-tests (4)
install-action: cargo-nextest is supported but version 0.9.143 for 'x86_64_linux' is not supported (updating install-action might resolve this); fallback to cargo-binstall
|