Skip to content
Continuous Integration Checks

Don't trim HTLCs when calculating the commit tx fee including the fee spike multiple #23048

Sign in to view logs

Don't trim HTLCs when calculating the commit tx fee including the fee spike multiple

Don't trim HTLCs when calculating the commit tx fee including the fee spike multiple #23048

Triggered via pull request April 24, 2026 17:31
@tankyleotankyleo
synchronize #4574
tankyleo:2026-04-reserve-breach
Status Success
Total duration 1h 31m 41s
Artifacts 1

build.yml

on: pull_request
fuzz
1h 6m
fuzz
Matrix: build-bindings / build
Matrix: build-cfg-flags / build
Matrix: build-features / build
Matrix: build-nostd / build
Matrix: build-sync / build
Matrix: build-workspace / build
ext-test
6m 42s
ext-test
benchmark
17m 37s
benchmark
check_release
2m 49s
check_release
check_docs
7m 25s
check_docs
fuzz_sanity
11m 37s
fuzz_sanity
linting
2m 32s
linting
rustfmt
13s
rustfmt
tor-connect
5m 39s
tor-connect
coverage
25m 26s
coverage
notify-failure
0s
notify-failure
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
rustfmt
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
check_release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
tor-connect
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
benchmark
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
benchmark
Failed to restore:
benchmark
Failed to restore:
build-workspace / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
build-bindings / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
build-features / build (self-hosted, 1.75.0)
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.
fuzz
Runner Version 2.331.0 will no longer be able to run jobs on April 29, 2026, please update your runner version.

Artifacts

Produced during runtime
Name Size Digest
hfuzz-corpus
36.5 MB
sha256:61c1eaa285e09d040f292cdcf3ac5f4c6c76244379b6d72c23eaacb49a265408