Skip to content

fatxpool: proper handling of priorities when mempool is full #9995

fatxpool: proper handling of priorities when mempool is full

fatxpool: proper handling of priorities when mempool is full #9995

Triggered via pull request December 4, 2024 17:14
Status Cancelled
Total duration 11m 17s
Artifacts

checks.yml

on: pull_request
preflight  /  preflight
39s
preflight / preflight
preflight  /  ci-versions
1m 24s
preflight / ci-versions
cargo-clippy
5m 58s
cargo-clippy
check-try-runtime
8m 14s
check-try-runtime
check-core-crypto-features
6m 19s
check-core-crypto-features
All checks passed
0s
All checks passed
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
cargo-clippy
Process completed with exit code 101.
check-try-runtime
The run was canceled by @paritytech-workflow-stopper[bot].
check-try-runtime
The operation was canceled.
preflight / preflight
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
preflight / ci-versions
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
cargo-clippy
Unexpected input(s) 'ref', 'inputs', valid inputs are ['route', 'mediaType']
cargo-clippy
This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0