Merge main into develop #3860
test-deployments.yml
on: pull_request
detect_deployments_changes
7s
test-evm-deployments
3m 49s
test-ccv-evm-deployments
3m 26s
test-solana-deployments
2m 48s
test-deployments
2m 43s
test-deployments-crosschain
4m 1s
Annotations
47 errors and 14 warnings
|
test-deployments
Process completed with exit code 1.
|
|
test-deployments
Failing the workflow as auto-quarantine is enabled, and junit-enhancer reported failures.
|
|
test-deployments
The JUnit Enhancer step failed. This is typically due to it detecting build failures or timeouts in the test reports.
|
|
test-deployments
The test results you are uploading contain non quarantined test failures -- see above for details.
|
|
test-deployments
Process completed with exit code 1.
|
|
test-deployments
JUnit XML enhancement completed with errors. See above logging for details.
|
|
test-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/deployment/v1_7_0/changesets - FAIL github.com/smartcontractkit/chainlink-ccip/deployment/v1_7_0/changesets [build failed]
|
|
test-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/deployment/lanes - FAIL github.com/smartcontractkit/chainlink-ccip/deployment/lanes [build failed]
|
|
test-deployments
Process completed with exit code 1.
|
|
test-deployments
not enough arguments in call to populateAddresses
|
|
test-deployments
not enough arguments in call to populateAddresses
|
|
test-solana-deployments
Process completed with exit code 1.
|
|
test-solana-deployments
Failing the workflow as auto-quarantine is enabled, and junit-enhancer reported failures.
|
|
test-solana-deployments
The JUnit Enhancer step failed. This is typically due to it detecting build failures or timeouts in the test reports.
|
|
test-solana-deployments
The test results you are uploading contain non quarantined test failures -- see above for details.
|
|
test-solana-deployments
Process completed with exit code 1.
|
|
test-solana-deployments
JUnit XML enhancement completed with errors. See above logging for details.
|
|
test-solana-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/sequences - FAIL github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/sequences [build fai... [truncated]
|
|
test-solana-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/changesets - FAIL github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/changesets [build fa... [truncated]
|
|
test-solana-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/adapters - FAIL github.com/smartcontractkit/chainlink-ccip/chains/solana/deployment/v1_6_0/adapters [build fail... [truncated]
|
|
test-solana-deployments
Process completed with exit code 1.
|
|
test-solana-deployments
not enough arguments in call to populateAddresses
|
|
test-solana-deployments
not enough arguments in call to populateAddresses
|
|
test-ccv-evm-deployments
Process completed with exit code 1.
|
|
test-evm-deployments
The JUnit Enhancer step failed. This is typically due to it detecting build failures or timeouts in the test reports.
|
|
test-evm-deployments
The test results you are uploading contain non quarantined test failures -- see above for details.
|
|
test-evm-deployments
Process completed with exit code 1.
|
|
test-evm-deployments
JUnit XML enhancement completed with errors. See above logging for details.
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v2_0_0/sequences - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v2_0_0/sequences [build failed... [truncated]
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v2_0_0/adapters - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v2_0_0/adapters [build failed]... [truncated]
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/sequences - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/sequences [build failed... [truncated]
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/changesets - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/changesets [build faile... [truncated]
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/adapters - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment/v1_6_0/adapters [build failed]... [truncated]
|
|
test-evm-deployments
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment - FAIL github.com/smartcontractkit/chainlink-ccip/chains/evm/deployment [build failed]
|
|
test-evm-deployments
Process completed with exit code 1.
|
|
test-evm-deployments
not enough arguments in call to populateAddresses
|
|
test-evm-deployments
not enough arguments in call to populateAddresses
|
|
test-deployments-crosschain
Process completed with exit code 1.
|
|
test-deployments-crosschain
Failing the workflow as auto-quarantine is enabled, and junit-enhancer reported failures.
|
|
test-deployments-crosschain
The JUnit Enhancer step failed. This is typically due to it detecting build failures or timeouts in the test reports.
|
|
test-deployments-crosschain
The test results you are uploading contain non quarantined test failures -- see above for details.
|
|
test-deployments-crosschain
Process completed with exit code 1.
|
|
test-deployments-crosschain
JUnit XML enhancement completed with errors. See above logging for details.
|
|
test-deployments-crosschain
(failing) Build failure detected for suite github.com/smartcontractkit/chainlink-ccip/integration-tests/deployment - FAIL github.com/smartcontractkit/chainlink-ccip/integration-tests/deployment [build failed]
|
|
test-deployments-crosschain
Process completed with exit code 1.
|
|
test-deployments-crosschain
not enough arguments in call to populateAddresses
|
|
test-deployments-crosschain
not enough arguments in call to populateAddresses
|
|
detect_deployments_changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36. 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/
|
|
test-deployments
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@0c52d547c9bc32b1aa3301fd7a9cb496313a4491, actions/upload-artifact@v5.0.0, trunk-io/analytics-uploader@293e9b144a101ef4b8fe3485a5afd0224fc48255. 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/
|
|
test-deployments
No files were found with the provided path: deployment/raw-test-logs/. No artifacts will be uploaded.
|
|
test-deployments
Failed to restore: Cache service responded with 400
|
|
test-solana-deployments
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@0c52d547c9bc32b1aa3301fd7a9cb496313a4491, actions/upload-artifact@v5.0.0, trunk-io/analytics-uploader@293e9b144a101ef4b8fe3485a5afd0224fc48255. 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/
|
|
test-solana-deployments
No files were found with the provided path: chains/solana/deployment/raw-test-logs/. No artifacts will be uploaded.
|
|
test-solana-deployments
Failed to restore: Cache service responded with 400
|
|
test-ccv-evm-deployments
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. 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/
|
|
test-evm-deployments
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@0c52d547c9bc32b1aa3301fd7a9cb496313a4491, actions/upload-artifact@v5.0.0, trunk-io/analytics-uploader@293e9b144a101ef4b8fe3485a5afd0224fc48255. 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/
|
|
test-evm-deployments
No files were found with the provided path: chains/evm/deployment/raw-test-logs/. No artifacts will be uploaded.
|
|
test-evm-deployments
Failed to restore: Cache service responded with 400
|
|
test-deployments-crosschain
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@0c52d547c9bc32b1aa3301fd7a9cb496313a4491, actions/upload-artifact@v5.0.0, trunk-io/analytics-uploader@293e9b144a101ef4b8fe3485a5afd0224fc48255. 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/
|
|
test-deployments-crosschain
No files were found with the provided path: integration-tests/deployment/raw-test-logs/. No artifacts will be uploaded.
|
|
test-deployments-crosschain
Failed to restore: Cache service responded with 400
|