Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mantle configs #15821

Closed
wants to merge 7 commits into from
Closed

Add mantle configs #15821

wants to merge 7 commits into from

Conversation

joaoluisam
Copy link
Contributor

No description provided.

@joaoluisam joaoluisam requested review from a team as code owners January 2, 2025 09:53
@joaoluisam joaoluisam requested a review from ilija42 January 2, 2025 09:53
@Bwest981 Bwest981 self-requested a review January 2, 2025 14:10
Bwest981
Bwest981 previously approved these changes Jan 2, 2025
ma33r
ma33r previously approved these changes Jan 2, 2025
@joaoluisam joaoluisam dismissed stale reviews from ma33r and Bwest981 via 7f9fbe4 January 2, 2025 17:57
jmank88
jmank88 previously approved these changes Jan 2, 2025
@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link
Contributor

github-actions bot commented Jan 6, 2025

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , GolangCI Lint (.) , test-scripts , Core Tests (go_core_tests) , 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. API server not ready yet (attempt 1-30):[go_core_tests_integration]

Source of Error:
Run tests	2025-01-06T14:33:54.8896842Z test_helpers.go:136: API server not ready yet (attempt 1): exit status 7
Run tests	2025-01-06T14:33:54.8897519Z test_helpers.go:136: API server not ready yet (attempt 2): exit status 7
Run tests	2025-01-06T14:33:54.8898309Z test_helpers.go:136: API server not ready yet (attempt 3): exit status 7
Run tests	2025-01-06T14:33:54.8898965Z test_helpers.go:136: API server not ready yet (attempt 4): exit status 7
Run tests	2025-01-06T14:33:54.8899752Z test_helpers.go:136: API server not ready yet (attempt 5): exit status 7
Run tests	2025-01-06T14:33:54.8900410Z test_helpers.go:136: API server not ready yet (attempt 6): exit status 7
Run tests	2025-01-06T14:33:54.8901207Z test_helpers.go:136: API server not ready yet (attempt 7): exit status 7
Run tests	2025-01-06T14:33:54.8901888Z test_helpers.go:136: API server not ready yet (attempt 8): exit status 7
Run tests	2025-01-06T14:33:54.8902557Z test_helpers.go:136: API server not ready yet (attempt 9): exit status 7
Run tests	2025-01-06T14:33:54.8903487Z test_helpers.go:136: API server not ready yet (attempt 10): exit status 7
Run tests	2025-01-06T14:33:54.8904176Z test_helpers.go:136: API server not ready yet (attempt 11): exit status 7
Run tests	2025-01-06T14:33:54.8904930Z test_helpers.go:136: API server not ready yet (attempt 12): exit status 7
Run tests	2025-01-06T14:33:54.8905589Z test_helpers.go:136: API server not ready yet (attempt 13): exit status 7
Run tests	2025-01-06T14:33:54.8906247Z test_helpers.go:136: API server not ready yet (attempt 14): exit status 7
Run tests	2025-01-06T14:33:54.8907022Z test_helpers.go:136: API server not ready yet (attempt 15): exit status 7
Run tests	2025-01-06T14:33:54.8907700Z test_helpers.go:136: API server not ready yet (attempt 16): exit status 7
Run tests	2025-01-06T14:33:54.8909225Z test_helpers.go:136: API server not ready yet (attempt 17): exit status 7
Run tests	2025-01-06T14:33:54.8909955Z test_helpers.go:136: API server not ready yet (attempt 18): exit status 7
Run tests	2025-01-06T14:33:54.8910719Z test_helpers.go:136: API server not ready yet (attempt 19): exit status 7
Run tests	2025-01-06T14:33:54.8911460Z test_helpers.go:136: API server not ready yet (attempt 20): exit status 7
Run tests	2025-01-06T14:33:54.8912121Z test_helpers.go:136: API server not ready yet (attempt 21): exit status 7
Run tests	2025-01-06T14:33:54.8912907Z test_helpers.go:136: API server not ready yet (attempt 22): exit status 7
Run tests	2025-01-06T14:33:54.8913571Z test_helpers.go:136: API server not ready yet (attempt 23): exit status 7
Run tests	2025-01-06T14:33:54.8914303Z test_helpers.go:136: API server not ready yet (attempt 24): exit status 7
Run tests	2025-01-06T14:33:54.8914995Z test_helpers.go:136: API server not ready yet (attempt 25): exit status 7
Run tests	2025-01-06T14:33:54.8915700Z test_helpers.go:136: API server not ready yet (attempt 26): exit status 7
Run tests	2025-01-06T14:33:54.8916518Z test_helpers.go:136: API server not ready yet (attempt 27): exit status 7
Run tests	2025-01-06T14:33:54.8917170Z test_helpers.go:136: API server not ready yet (attempt 28): exit status 7
Run tests	2025-01-06T14:33:54.8917929Z test_helpers.go:136: API server not ready yet (attempt 29): exit status 7
Run tests	2025-01-06T14:33:54.8918614Z test_helpers.go:136: API server not ready yet (attempt 30): exit status 7

Why: The API server failed to start within the expected time frame, likely due to the address 127.0.0.1:53792 being already in use, causing the server to be unable to bind to the required port.

Suggested fix: Ensure that the port 53792 is free before starting the API server. Alternatively, configure the server to use a different port that is not in use.

@joaoluisam joaoluisam closed this Jan 6, 2025
@joaoluisam joaoluisam deleted the INTAUTO-370-Add-mantle-configs branch January 6, 2025 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants