-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
ccip - rmn cursing support #15263
ccip - rmn cursing support #15263
Conversation
I see you updated files related to
|
AER Report: CI Coreaer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Flakeguard Deployment Project / Get Tests To Run , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , Flakeguard Deployment Project / Run Tests (github.com/smartcontractkit/chainlink/deployment/ccip/changeset, ubuntu-latest) , Flakey Test Detection , SonarQube Scan , Flakeguard Deployment Project / Report 1. Error stopping job service:[Run tests with flakeguard]Source of Error:
Why: The error occurs because the job service is being stopped multiple times, leading to repeated attempts to close the RMN home reader, which has already been stopped. Suggested fix: Ensure that the job service stop logic checks if the service is already stopped before attempting to stop it again. This can prevent redundant stop attempts and avoid the error. 2. Connection refused:[Run tests with flakeguard]Source of Error:
Why: The error indicates that the connection attempt to the specified address and port was refused, likely because the service at that address is not running or not accepting connections. Suggested fix: Ensure that the service at 3. Use of closed network connection:[Run tests with flakeguard]Source of Error:
Why: This error occurs when an attempt is made to read from a network connection that has already been closed, indicating a premature closure or a race condition in the connection handling. Suggested fix: Ensure proper synchronization and lifecycle management of network connections. Avoid closing connections prematurely and handle connection closures gracefully. 4. Test failure:[Run tests with flakeguard]Source of Error:
Why: The test Suggested fix: Investigate the AER Report: Operator UI CI ran successfully ✅ |
requires: smartcontractkit/chainlink-ccip#317