Fix concurrent_delete_gauge

[samsondav]

Requires

Supports

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube

[github-actions]

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , Core Tests (go_core_tests) , test-scripts , GolangCI Lint (.) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , lint , SonarQube Scan

1. Context deadline exceeded error:[go_core_ccip_deployment_tests]

Source of Error:

Run tests	2025-01-24T20:33:39.5344556Z --- FAIL: TestDeployLinkToken (44.15s)
Run tests	2025-01-24T20:33:39.5344922Z chain.go:136: 
Run tests	2025-01-24T20:33:39.5348969Z 	Error Trace:	/home/runner/work/chainlink/chainlink/deployment/environment/memory/chain.go:210
Run tests	2025-01-24T20:33:39.5350290Z 	 				/home/runner/work/chainlink/chainlink/deployment/environment/memory/chain.go:136
Run tests	2025-01-24T20:33:39.5351553Z 	 				/home/runner/work/chainlink/chainlink/deployment/environment/memory/environment.go:84
Run tests	2025-01-24T20:33:39.5352821Z 	 				/home/runner/work/chainlink/chainlink/deployment/environment/memory/environment.go:215
Run tests	2025-01-24T20:33:39.5354177Z 	 				/home/runner/work/chainlink/chainlink/deployment/common/changeset/deploy_link_token_test.go:17
Run tests	2025-01-24T20:33:39.5354794Z 	Error: 	Received unexpected error:
Run tests	2025-01-24T20:33:39.5355657Z 	 	start container: started hook: wait until ready: context deadline exceeded
Run tests	2025-01-24T20:33:39.5356160Z 	Test: 	TestDeployLinkToken

Why: The error "context deadline exceeded" indicates that the test TestDeployLinkToken failed because a container did not start within the expected time frame. This could be due to resource constraints, network issues, or misconfiguration in the test environment.

Suggested fix: Increase the timeout duration for the container startup in the test configuration. Additionally, ensure that the test environment has sufficient resources and that there are no network issues affecting container startup.