-
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
core/services/ocr2/plugins/ccip: parallelize tests #15757
Conversation
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
AER Report: CI Coreaer_workflow , commit , Detect Changes , Scheduled Run Frequency , Clean Go Tidy & Generate , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Flakeguard Deployment Project , 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/ocr2/plugins/ccip, ubuntu-latest) , Flakey Test Detection , SonarQube Scan , Flakeguard Root Project / Report 1. Flaky tests below pass ratio threshold:Run tests with flakeguardSource of Error:
Why: The error occurred because there were 5 flaky tests that did not meet the required pass ratio threshold of 1.00. These tests had inconsistent results across multiple runs, leading to a failure in the overall test suite. Suggested fix: Investigate the flaky tests to identify the root cause of their instability. This may involve reviewing the test code for race conditions, dependencies on external systems, or other factors that could cause intermittent failures. Stabilize the tests to ensure consistent pass rates. |
No description provided.