Skip to content

fix: potential max block size #14151

fix: potential max block size

fix: potential max block size #14151

Triggered via pull request December 13, 2024 09:52
Status Success
Total duration 24m 40s
Artifacts 5

ci.yml

on: pull_request
clippy
7m 4s
clippy
machete
31s
machete
cargo check with stable
6m 27s
cargo check with stable
file licenses
5s
file licenses
pr_2_artifact
3s
pr_2_artifact
Upload Event File for Test Results
2s
Upload Event File for Test Results
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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
pr_2_artifact
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
clippy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test (testnet, esmeralda)
Failed to restore: ENOENT: no such file or directory, scandir '/opt/hostedtoolcache/tari-project/tari'

Artifacts

Produced during runtime
Name Size
Event File
3.69 KB
pr_num
141 Bytes
test-results-mainnet.stagenet
27 KB
test-results-nextnet.nextnet
25.5 KB
test-results-testnet.esmeralda
26.7 KB