Skip to content
SDK

CLI - loader v3 to v4 migration #379

Sign in to view logs

CLI - loader v3 to v4 migration

CLI - loader v3 to v4 migration #379

Triggered via pull request February 7, 2025 22:23
@LichtsoLichtso
synchronize #4856
Lichtso:cli/loader_v3_to_v4_migration
Status Success
Total duration 40m 0s
Artifacts –

sdk.yml

on: pull_request
Sanity checks
40s
Sanity checks
Check crate ownership
1m 23s
Check crate ownership
Cargo check
1m 19s
Cargo check
Format
18s
Format
Audit
18s
Audit
Check semver
0s
Check semver
Cargo hack check
3m 13s
Cargo hack check
Check crate dependencies for publishing
13s
Check crate dependencies for publishing
Check sorting of crate dependencies
26s
Check sorting of crate dependencies
Check declarations of `dev-context-only-utils` feature
29s
Check declarations of `dev-context-only-utils` feature
Matrix: Clippy
Test miri
1m 3s
Test miri
Run frozen-abi tests
1m 40s
Run frozen-abi tests
Build wasm packages and run tests
3m 19s
Build wasm packages and run tests
Run coverage tests
3m 48s
Run coverage tests
Run tests on stable toolchain
2m 2s
Run tests on stable toolchain
Run benches
5m 40s
Run benches
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
Sanity checks
Failed to restore: Cache service responded with 429
Check crate ownership
Failed to restore: Cache service responded with 429
Check crate ownership
Failed to restore: Cache service responded with 429
Clippy (windows-latest)
Failed to restore: Cache service responded with 429
Audit
Failed to restore: Cache service responded with 429
Check declarations of `dev-context-only-utils` feature
Failed to restore: Cache service responded with 429
Format
Failed to restore: Cache service responded with 429
Cargo check
Failed to restore: Cache service responded with 429
Clippy (ubuntu-latest)
Failed to restore: Cache service responded with 429
Cargo hack check
Failed to restore: Cache service responded with 429
Test miri
Failed to restore: Cache service responded with 429
Run frozen-abi tests
Failed to restore: Cache service responded with 429
Run tests on stable toolchain
Failed to restore: Cache service responded with 429
Run tests on stable toolchain
Failed to save: Cache service responded with 429 during commit cache.
Build wasm packages and run tests
Failed to restore: Cache service responded with 429
Build wasm packages and run tests
Failed to restore: Cache service responded with 429
Build wasm packages and run tests
Failed to save: Cache service responded with 429 during commit cache.
Run coverage tests
Failed to restore: Cache service responded with 429
Run coverage tests
Failed to restore: Cache service responded with 429
Run benches
Failed to restore: Cache service responded with 429