Integration In-Memory Tests #39448
integration-in-memory-tests.yml
on: pull_request
Check Paths That Require Tests To Run
7s
Run CCIP Integration In Memory Tests For Merge Queue
/
Validate workflow inputs
Run CCIP integration In Memory Tests For PR
/
Validate workflow inputs
3s
Run CCIP Integration In Memory Tests For Merge Queue
/
Get latest Chainlink release version
Run CCIP integration In Memory Tests For PR
/
Get latest Chainlink release version
4s
Run CCIP Integration In Memory Tests For Merge Queue
/
Load test configurations
Run CCIP Integration In Memory Tests For Merge Queue
/
Check test configurations
Run CCIP integration In Memory Tests For PR
/
Load test configurations
36s
Run CCIP integration In Memory Tests For PR
/
Check test configurations
Matrix: Run CCIP Integration In Memory Tests For Merge Queue / Get Chainlink image
Waiting for pending jobs
Matrix: Run CCIP Integration In Memory Tests For Merge Queue / Get Chainlink plugins image
Waiting for pending jobs
Matrix: Run CCIP Integration In Memory Tests For Merge Queue / run-in-memory-tests
Waiting for pending jobs
Run CCIP Integration In Memory Tests For Merge Queue
/
Get remote runner test image
Matrix: Run CCIP integration In Memory Tests For PR / Get Chainlink image
Matrix: Run CCIP integration In Memory Tests For PR / Get Chainlink plugins image
Matrix: Run CCIP integration In Memory Tests For PR / run-in-memory-tests
Run CCIP integration In Memory Tests For PR
/
Get remote runner test image
Matrix: Run CCIP Integration In Memory Tests For Merge Queue / run-docker-tests
Waiting for pending jobs
Matrix: Run CCIP Integration In Memory Tests For Merge Queue / run-k8s-runner-tests
Waiting for pending jobs
Matrix: Run CCIP integration In Memory Tests For PR / run-docker-tests
Matrix: Run CCIP integration In Memory Tests For PR / run-k8s-runner-tests
Run CCIP Integration In Memory Tests For Merge Queue
/
After tests
Run CCIP integration In Memory Tests For PR
/
After tests
5s
Integration Tests
4s
Annotations
3 errors and 3 warnings
|
Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_sui_upgrade_test.go:Test_CCIP_Upgrade_EVM2Sui
A failure occurred while executing the command -- see above for details
|
|
Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_sui_upgrade_test.go:Test_CCIP_Upgrade_EVM2Sui
Process completed with exit code 1.
|
|
Integration Tests
Process completed with exit code 1.
|
|
Run CCIP integration In Memory Tests For PR / smoke/ccip/ccip_sui_upgrade_test.go:Test_CCIP_Upgrade_EVM2Sui
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/setup-go@v5, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@010d0da01d0b5a38af31e9c3470dbfdabdecca3a, azure/setup-helm@29960d0f5f19214b88e1d9ba750a9914ab0f1a2f, jwalton/gh-docker-logs@2741064ab9d7af54b0b1ffb6076cf64c16f0220e, runs-on/action@66d4449b717b5462159659523d1241051ff470b9, trunk-io/analytics-uploader@f2631c653f9675d391e6e68cc877370db927c64c. 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/
|
|
LaunchWarning
Dropped incompatible instance families: m5.* (no such instance type exists in this region). Proceeding with: m6i.
|
|
Run CCIP integration In Memory Tests For PR / After tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4.1.8. 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 | |
|---|---|---|---|
|
smoke_ccip_ccip_sui_upgrade_test_go_Test_CCIP_Upgrade_EVM2Sui-test-logs
|
58.4 MB |
sha256:7c04f684d047e527926521ed019344b850a43eb5252890205015828c82f1569c
|
|