chore: reduce e2e flakiness & log verbosity#1881
Merged
Merged
Conversation
We had the replay test failing more often than expected due to racing conditions between our tests and the inserts in the database which lead to a higher failure rate. This also reduces the log noise to be more single line focused instead of tables and more noise that it's not useful for the e2e usecase
filipecabaco
force-pushed
the
chore/reduce-e2e-flakiness
branch
from
41aacb5 to
c0a39a6
Compare
|
coverage: 91.226% (-0.06%) from 91.284% — chore/reduce-e2e-flakiness into main |
leandrocp
approved these changes
May 19, 2026
|
🎉 This PR is included in version 2.96.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
3 participants
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.
What kind of change does this PR introduce?
We had the replay test failing more often than expected due to racing conditions between our tests and the inserts in the database which lead to a higher failure rate.
This also reduces the log noise to be more single line focused instead of tables and more noise that it's not useful for the e2e usecase