Skip to content

Fix unfail retry when deployment head behind error block #11621

Fix unfail retry when deployment head behind error block

Fix unfail retry when deployment head behind error block #11621

Triggered via pull request April 21, 2026 10:13
Status Cancelled
Total duration 58s
Artifacts

ci.yml

on: pull_request
Run unit tests
43s
Run unit tests
Subgraph Runner integration tests
42s
Subgraph Runner integration tests
Run integration tests
50s
Run integration tests
Check rustfmt style
24s
Check rustfmt style
Clippy linting
47s
Clippy linting
Build in release mode
49s
Build in release mode
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 2 warnings
Clippy linting
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/merge exists
Clippy linting
The operation was canceled.
Subgraph Runner integration tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/merge exists
Subgraph Runner integration tests
The operation was canceled.
Run unit tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/merge exists
Run unit tests
The operation was canceled.
Build in release mode
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/merge exists
Build in release mode
The operation was canceled.
Run integration tests
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/merge exists
Run integration tests
The operation was canceled.
Continuous Integration
Canceling since a higher priority waiting request for Continuous Integration-refs/pull/6529/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/
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/