Conversation
This reverts commit d8bd2d5.
…in-core-with-Flakeguard
|
chainchad
approved these changes
Apr 1, 2025
sebawo
approved these changes
Apr 1, 2025
jmank88
approved these changes
Apr 1, 2025
leeyikjiun
approved these changes
Apr 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





This pull request introduces Flakeguard auto-reruns for both in-memory and Docker-based end-to-end (e2e) tests for the merge queue. This enhancement aims to improve the reliability and stability of our CI/CD pipeline by automatically retrying tests identified as flaky, reducing the likelihood of false failures blocking merges.
Key Changes:
test_go_project_pathfield in integration-in-memory.yml and e2e-tests.yml test definitions. You can read more about this field in the E2E Workflow DocMotivation:
Flaky tests have been a recurring issue, leading to unnecessary delays and manual interventions in the merge queue. By automating the retry process for these tests, we can: