Skip to content

Add Rust ABI support for WASM subgraphs #11456

Add Rust ABI support for WASM subgraphs

Add Rust ABI support for WASM subgraphs #11456

Triggered via pull request March 28, 2026 17:34
Status Cancelled
Total duration 1m 43s
Artifacts

ci.yml

on: pull_request
Run unit tests
1m 25s
Run unit tests
Subgraph Runner integration tests
1m 27s
Subgraph Runner integration tests
Run integration tests
1m 26s
Run integration tests
Check rustfmt style
26s
Check rustfmt style
Clippy linting
1m 39s
Clippy linting
Build in release mode
1m 37s
Build in release mode
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 19 warnings
Check rustfmt style
Process completed with exit code 1.
Run unit tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Run unit tests
The operation was canceled.
Subgraph Runner integration tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Subgraph Runner integration tests
The operation was canceled.
Run integration tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Run integration tests
The operation was canceled.
Build in release mode
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Build in release mode
The operation was canceled.
Clippy linting
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Clippy linting
The operation was canceled.
Continuous Integration
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6462/merge exists
Check rustfmt style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@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 rustfmt style: runtime/wasm/src/rust_abi/host.rs#L21
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/rust_abi/host.rs
Check rustfmt style: runtime/wasm/src/module/instance.rs#L540
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/module/instance.rs
Check rustfmt style: runtime/wasm/src/module/instance.rs#L218
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/module/instance.rs
Check rustfmt style: runtime/wasm/src/module/context.rs#L1404
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/module/context.rs
Check rustfmt style: runtime/wasm/src/module/context.rs#L1289
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/module/context.rs
Check rustfmt style: runtime/wasm/src/mapping.rs#L317
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/mapping.rs
Check rustfmt style: runtime/wasm/src/mapping.rs#L279
Diff in /home/runner/work/graph-node/graph-node/runtime/wasm/src/mapping.rs
Check rustfmt style: chain/ethereum/src/trigger.rs#L672
Diff in /home/runner/work/graph-node/graph-node/chain/ethereum/src/trigger.rs
Check rustfmt style: chain/ethereum/src/trigger.rs#L23
Diff in /home/runner/work/graph-node/graph-node/chain/ethereum/src/trigger.rs
Check rustfmt style: chain/ethereum/src/runtime/runtime_adapter.rs#L267
Diff in /home/runner/work/graph-node/graph-node/chain/ethereum/src/runtime/runtime_adapter.rs
Run unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
Run unit tests
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
Subgraph Runner integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
Subgraph Runner integration tests
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
Run integration tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, extractions/setup-crate@v1, foundry-rs/foundry-toolchain@82dee4ba654bd2146511f85f0d013af94670c4de, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. 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/
Run integration tests
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1
Build in release mode
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@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/
Clippy linting
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@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/