-
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
[CAPPL-324] Fix panic when fetching binary #15490
Conversation
cedric-cordenier
commented
Dec 3, 2024
•
edited
Loading
edited
- Fix panic when fetching binary
- Lazy load the connector by creating a FetcherService, and starting it after the GatewayConnector starts. This avoids GatewayConnector being nil and prevents us from panicking when calling Fetch.
- Add some logging
- Remove logging of the request/response body -- this was causing my local node to crash since the body was so large.
AER Report: CI Coreaer_workflow , commit , Scheduled Run Frequency , Clean Go Tidy & Generate , Detect Changes , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Flakeguard Deployment Project , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/relay/evm/capabilities/workflow... , Flakeguard Root Project / Run Tests (github.com/smartcontractkit/chainlink/v2/core/services/workflows/syncer, ubuntu-latest) , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan 1. Error running tests: failed to parse test results: failed to attribute panic to test[A 1 <= 10 words sentence that describes the error]:[Run tests with flakeguard] Source of Error:
Why: The error occurred because there was a panic in the test Suggested fix: Ensure that all goroutines are properly synchronized and terminated before the test completes. This can be done by using synchronization mechanisms like AER Report: Operator UI CI ran successfully ✅ |
9cd062d
to
428ca3c
Compare
428ca3c
to
ce1bdb8
Compare
- Stop logging out the request/response body - Add a timeout when fetching the request - Add the method in various places where it was missing
40f5583
to
9a1d94c
Compare
Flakeguard Summary
Found Flaky Tests ❌
|
4846e34
to
27b86a0
Compare
Hey @cedric-cordenier! It looks like our internal flaky test detection tool, Flakeguard, has a bug. We're working on a fix. In the meantime, you can ignore these results. |