Skip to content

fuzz: Add upgrade/downgrade simulation to chanmon_consistency and fix chacha20 build #22628

fuzz: Add upgrade/downgrade simulation to chanmon_consistency and fix chacha20 build

fuzz: Add upgrade/downgrade simulation to chanmon_consistency and fix chacha20 build #22628

Triggered via pull request March 25, 2026 18:54
Status Cancelled
Total duration 9m 47s
Artifacts

build.yml

on: pull_request
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
coverage
0s
coverage
notify-failure
notify-failure
Fit to window
Zoom out
Zoom in

Annotations

25 errors and 5 warnings
benchmark
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
benchmark
The operation was canceled.
build-bindings / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-bindings / build (self-hosted, 1.75.0)
The operation was canceled.
fuzz
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
fuzz
The operation was canceled.
fuzz_sanity
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
fuzz_sanity
The operation was canceled.
build-features / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-features / build (self-hosted, 1.75.0)
The operation was canceled.
build-workspace / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-workspace / build (self-hosted, 1.75.0)
The operation was canceled.
build-nostd / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-nostd / build (self-hosted, 1.75.0)
The operation was canceled.
build-cfg-flags / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-cfg-flags / build (self-hosted, 1.75.0)
The operation was canceled.
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
Continuous Integration Checks
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-sync / build (self-hosted, 1.75.0)
Canceling since a higher priority waiting request for Continuous Integration Checks-refs/pull/4499/merge exists
build-sync / build (self-hosted, 1.75.0)
The operation was canceled.
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. 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. 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/