-
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
[TT-1952] try to split logs by level in in-memory tests [WIP] #16029
base: develop
Are you sure you want to change the base?
Conversation
AER Report: CI Coreaer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , GolangCI Lint (.) , Core Tests (go_core_tests) , GolangCI Lint (integration-tests) , Core Tests (go_core_tests_integration) , GolangCI Lint (deployment) , test-scripts , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , lint , SonarQube Scan 1. Comment formatting issue: Golang Lint (deployment)Source of Error:
Why: The linter detected a comment formatting issue where there is no space between Suggested fix: Add a space between 2. Test failure due to missing directory: Core Tests (go_core_ccip_deployment_tests)Source of Error:
Why: The test failed because it attempted to create a debug log file in a directory that does not exist. Suggested fix: Ensure that the directory 3. Test failure due to missing directory: Core Tests (go_core_ccip_deployment_tests)Source of Error:
Why: The test failed because it attempted to create a debug log file in a directory that does not exist. Suggested fix: Ensure that the directory 4. Test failure due to missing directory: Core Tests (go_core_ccip_deployment_tests)Source of Error:
Why: The test failed because it attempted to create a debug log file in a directory that does not exist. Suggested fix: Ensure that the directory 5. Test failure due to timeout: Core Tests (go_core_tests)Source of Error:
Why: The test failed due to a timeout, indicating that it took too long to complete. Suggested fix: Investigate the test to identify any performance bottlenecks or infinite loops. Optimize the code or increase the timeout duration if necessary. AER Report: Operator UI CI ran successfully ✅ |
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. |
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. |
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. |
Quality Gate failedFailed conditions See analysis details on SonarQube Catch issues before they fail your Quality Gate with our IDE extension SonarLint |
DO NOT REVIEW
Trying out some ideas.