Skip to content

drop cap registry field from relayer #6933

drop cap registry field from relayer

drop cap registry field from relayer #6933

Triggered via pull request April 8, 2026 13:03
Status Failure
Total duration 8m 3s
Artifacts 1

e2e_custom_cl.yml

on: pull_request
Check for contract changes
3s
Check for contract changes
Check integration test compilation
1m 58s
Check integration test compilation
Get ProjectSerum Version
8s
Get ProjectSerum Version
E2E Custom Build Artifacts
5m 26s
E2E Custom Build Artifacts
E2E Build Previous Release Artifacts
0s
E2E Build Previous Release Artifacts
E2E Custom Build Custom CL Image
7m 14s
E2E Custom Build Custom CL Image
Combine artifacts for upgrade test
Combine artifacts for upgrade test
E2E Custom Run Smoke Tests
2s
E2E Custom Run Smoke Tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 7 warnings
E2E Custom Build Custom CL Image
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c mkdir -p /gobins && if [ \"$CL_IS_PROD_BUILD\" = \"false\" ]; then GOBIN=/gobins make install-chainlink-dev; else GOBIN=/gobins make install-chainlink; fi" did not complete successfully: exit code: 2
E2E Custom Build Custom CL Image
too many arguments in call to solana.NewRelayer
E2E Custom Build Custom CL Image
too many arguments in call to solana.NewRelayer
E2E Custom Run Smoke Tests
Process completed with exit code 1.
Check for contract changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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 for contract changes
'base' input parameter is ignored when action is triggered by pull request event
Get Core Ref
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/
Get ProjectSerum Version
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 integration test compilation
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/setup-go@v5. 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/
E2E Custom Build Artifacts
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/upload-artifact@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/
E2E Custom Build Custom CL Image
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076, aws-actions/configure-aws-credentials@b47578312673ae6fa5b5096b330d9fbac3d116df, docker/metadata-action@369eb591f429131d6889c46b94e711f089e6ca96, docker/setup-buildx-action@f7ce87c1d6bead3e36075b2ce75da1f6cc28aaca. 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/

Artifacts

Produced during runtime
Name Size Digest
artifacts
747 KB
sha256:9d735130d441bf2bab6a323704f1a50ba87a075a5cf428f986704232f8fb324f