Skip to content
Run CI - Integration Tests

feat: initial attempt at replicator integration #3516

Sign in to view logs

feat: initial attempt at replicator integration

feat: initial attempt at replicator integration #3516

Triggered via pull request April 1, 2026 08:37
@bmuddhabmuddha
synchronize #1049
bmuddha/replicator/integration
Status Cancelled
Total duration 9m 23s
Artifacts –

ci-test-integration.yml

on: pull_request
Build Project
4m 36s
Build Project
Matrix: run_integration_tests
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 13 warnings
Integration Tests - config
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - config
The operation was canceled.
Integration Tests - cloning
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - cloning
The operation was canceled.
Integration Tests - magicblock_api
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - magicblock_api
The operation was canceled.
Integration Tests - table_mania
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - table_mania
The operation was canceled.
Integration Tests - schedule_intents
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - schedule_intents
The operation was canceled.
Integration Tests - restore_ledger
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - restore_ledger
The operation was canceled.
Integration Tests - task-scheduler
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - task-scheduler
The operation was canceled.
Integration Tests - committor
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - committor
The operation was canceled.
Integration Tests - chainlink
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - chainlink
The operation was canceled.
Integration Tests - schedulecommit
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - schedulecommit
The operation was canceled.
Run CI - Integration Tests
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - pubsub
Canceling since a higher priority waiting request for Run CI - Integration Tests-refs/pull/1049/merge exists
Integration Tests - pubsub
The operation was canceled.
Build Project
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - config
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - cloning
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - magicblock_api
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - table_mania
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - schedule_intents
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - restore_ledger
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - task-scheduler
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - committor
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - chainlink
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - schedulecommit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - pubsub
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-gw/setup-protoc-to-env@v3. 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/
Integration Tests - pubsub
Failed to save: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 1