tests: remove flakyness from kafka tests#2647
Merged
Merged
Conversation
The Kafka clients could be created/subscribed before topics existed, while fixed topic names also leaked broker state because Kafka topic deletion is async. So make topic names unique, wait for consumer partition assignment before producing and remember to close the kafka clients on teardown. Assisted-by: Cursor
🤖 GitHub commentsJust comment with:
|
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
2 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 does this pull request do?
The Kafka clients could be created/subscribed before topics existed, while fixed topic names also leaked broker state because Kafka topic deletion is async.
So make topic names unique, wait for consumer partition assignment before producing and remember to close the kafka clients on teardown.
Assisted-by: Cursor
Related issues
Closes #2630