Skip to content

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

fatxpool: proper handling of priorities when mempool is full

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

Triggered via pull request November 28, 2024 17:31
Status Cancelled
Total duration 14m 32s
Artifacts 3

subsystem-benchmarks.yml

on: pull_request
preflight  /  preflight
40s
preflight / preflight
preflight  /  ci-versions
1m 0s
preflight / ci-versions
Matrix: build
publish-benchmarks
0s
publish-benchmarks
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build (polkadot-node-core-approval-voting, approval-voting-regression-bench)
The run was canceled by @paritytech-workflow-stopper[bot].
preflight / preflight
Unable to find merge base between 8216235b480630c5a69636b172f5146711c88c9a and eecc8491ccf58990697f4c700a1191f56937884a

Artifacts

Produced during runtime
Name Size
availability-distribution-regression-bench
407 Bytes
availability-recovery-regression-bench
351 Bytes
statement-distribution-regression-bench
353 Bytes