Skip to content

Implement dynamic storage based StorageVec #26811

Implement dynamic storage based StorageVec

Implement dynamic storage based StorageVec #26811

Triggered via pull request April 30, 2026 10:37
Status Failure
Total duration 22m 30s
Artifacts –

ci.yml

on: pull_request
get-fuel-core-version
46s
get-fuel-core-version
build-sway-lib-std
1m 49s
build-sway-lib-std
build-sway-examples
1m 6s
build-sway-examples
cargo-build-workspace
1m 11s
cargo-build-workspace
cargo-clippy
4m 59s
cargo-clippy
cargo-test-lib-std
9m 18s
cargo-test-lib-std
cargo-unused-deps-check
10m 25s
cargo-unused-deps-check
cargo-fmt-check
17s
cargo-fmt-check
pre-publish-check
0s
pre-publish-check
forc-run-benchmarks
5m 12s
forc-run-benchmarks
check-dependency-version-formats
46s
check-dependency-version-formats
check-forc-manifest-version
23s
check-forc-manifest-version
build-reference-examples
51s
build-reference-examples
forc-fmt-check-sway-lib-std
3m 46s
forc-fmt-check-sway-lib-std
forc-fmt-check-sway-examples
3m 47s
forc-fmt-check-sway-examples
forc-fmt-check-panic
6m 12s
forc-fmt-check-panic
check-sdk-harness-test-suite-compatibility
49s
check-sdk-harness-test-suite-compatibility
build-mdbook
9m 16s
build-mdbook
build-forc-doc-sway-lib-std
5m 9s
build-forc-doc-sway-lib-std
forc-unit-tests
22m 21s
forc-unit-tests
forc-pkg-fuels-deps-check
30s
forc-pkg-fuels-deps-check
cargo-toml-fmt-check
28s
cargo-toml-fmt-check
Matrix: Build and test various forc tools
cargo-run-e2e-test
10m 33s
cargo-run-e2e-test
cargo-run-e2e-test-release
8m 4s
cargo-run-e2e-test-release
publish
publish
notify-slack-on-failure
notify-slack-on-failure
Matrix: Build and upload forc binaries to release
verifications-complete
0s
verifications-complete
publish-sway-lib-std
0s
publish-sway-lib-std
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 15 warnings
forc-fmt-check-sway-lib-std
Process completed with exit code 1.
Build and test various forc tools (cargo test --locked --release -p forc-debug)
The strategy configuration was canceled because "cargo-test-tools.cargo_nextest_run_--locke" failed
Build and test various forc tools (cargo test --locked --release --workspace --exclude forc-debug...
The strategy configuration was canceled because "cargo-test-tools.cargo_nextest_run_--locke" failed
forc-unit-tests
Process completed with exit code 1.
cargo-toml-fmt-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: baptiste0928/cargo-install@v1. 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/
cargo-toml-fmt-check
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DzHzaQAAAACiV1qMHWpIQ5iw1d6UNRhMUEFPRURHRTA2MjAARWRnZQ==
cargo-toml-fmt-check
Failed to restore: Cache service responded with 400
check-sdk-harness-test-suite-compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/toolchain@v1. 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-sdk-harness-test-suite-compatibility
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-sdk-harness-test-suite-compatibility
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-sdk-harness-test-suite-compatibility
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
check-sdk-harness-test-suite-compatibility
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build and test various forc tools (cargo test --locked --release -p forc -- --nocapture)
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/
Build and test various forc tools (cargo nextest run --locked --release -p sway-lsp --no-capture ...
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/
Build and test various forc tools (cargo test --locked --release -p forc-debug)
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/
Build and test various forc tools (cargo test --locked --release --workspace --exclude forc-debug...
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/
forc-run-benchmarks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: EndBug/add-and-commit@v9. 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/
forc-run-benchmarks
Failed to restore: Cache service responded with 404
build-mdbook
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: peaceiris/actions-mdbook@v1. 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/