test if port healthcheck works, remove 2 EVM networks, keep only one

[skudasov]

No description provided.

[github-actions]

AER Report: Operator UI CI

aer_workflow , commit , Breaking Changes GQL Check

1. Workflow failed to complete successfully:[convictional/trigger-workflow-and-wait@f69fa9e]

Source of Error:

Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-11T16:09:01.7173190Z Checking conclusion [failure]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-11T16:09:01.7173894Z Checking status [completed]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-11T16:09:01.7174793Z Conclusion is not success, it's [failure].
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2024-11-11T16:09:01.7175508Z Propagating failure to upstream job

Why: The triggered workflow did not complete successfully. The status was checked multiple times and eventually concluded with a failure status.

Suggested fix: Investigate the logs of the downstream workflow (ID: 11782110055) to identify the specific cause of failure and address the underlying issue.

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , lint , Core Tests (go_core_tests) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , SonarQube Scan

1. Ambiguous import in e2e module: [job id where the error happened]

Source of Error:

Run make gomodtidy	2024-11-11T16:16:56.0191960Z 	go: github.com/smartcontractkit/chainlink/e2e/capabilities/components/onchain imports
Run make gomodtidy	2024-11-11T16:16:56.0192914Z 		github.com/ethereum/go-ethereum/crypto imports
Run make gomodtidy	2024-11-11T16:16:56.0193403Z 		github.com/btcsuite/btcd/btcec/v2/ecdsa tested by
Run make gomodtidy	2024-11-11T16:16:56.0193898Z 		github.com/btcsuite/btcd/btcec/v2/ecdsa.test imports
Run make gomodtidy	2024-11-11T16:16:56.0194920Z 		github.com/btcsuite/btcd/chaincfg/chainhash: ambiguous import: found package github.com/btcsuite/btcd/chaincfg/chainhash in multiple modules:
Run make gomodtidy	2024-11-11T16:16:56.0196294Z 		github.com/btcsuite/btcd v0.22.0-beta (/home/runner/go/pkg/mod/github.com/btcsuite/[email protected]/chaincfg/chainhash)
Run make gomodtidy	2024-11-11T16:16:56.0197530Z 		github.com/btcsuite/btcd/chaincfg/chainhash v1.0.1 (/home/runner/go/pkg/mod/github.com/btcsuite/btcd/chaincfg/[email protected])
Run make gomodtidy	2024-11-11T16:16:56.0198294Z 	error: exit status 1

Why: The error is caused by an ambiguous import of the chainhash package from two different versions of the btcsuite/btcd module. This conflict arises because the go.mod file includes dependencies that import different versions of the same package.

Suggested fix: Resolve the ambiguous import by ensuring that only one version of the btcsuite/btcd module is used across all dependencies. Update the go.mod file to specify a single version and run go mod tidy again.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube