Schema Tracking Flaky Test: Ignore unrelated gtid progress events #8283
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.
Description
This PR is an attempt to fix the flakiness detected recently in
TestSchemaVersioning
such asLocal failures indicate this is happening due to an additional BEGIN/GTID/COMMIT group of events that happens at different times in the test causing event comparisons to fail at different points in that test. It is not clear what is causing it: it could be some
_vt
schema changes or some unrelated dmls from parallel or teardowns previous tests that are running concurrently.This PR ignores such gtid progress events that can race with the events that the schema versioning test expects.
Signed-off-by: Rohit Nayak [email protected]