Skip to content

fix: potential max block size #14144

fix: potential max block size

fix: potential max block size #14144

Triggered via pull request December 12, 2024 14:14
Status Failure
Total duration 14m 17s
Artifacts 5

ci.yml

on: pull_request
clippy
37s
clippy
machete
1m 36s
machete
cargo check with stable
8m 44s
cargo check with stable
file licenses
11s
file licenses
pr_2_artifact
4s
pr_2_artifact
Upload Event File for Test Results
5s
Upload Event File for Test Results
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
clippy
Process completed with exit code 1.
pr_2_artifact
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Upload Event File for Test Results
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
clippy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
machete
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
cargo check with stable
Failed to restore: ENOENT: no such file or directory, scandir '/opt/hostedtoolcache/tari-project/tari'

Artifacts

Produced during runtime
Name Size
Event File
3.8 KB
pr_num
141 Bytes
test-results-mainnet.stagenet
26.3 KB
test-results-nextnet.nextnet
26.6 KB
test-results-testnet.esmeralda
26.2 KB