KAFKA-18568 Flaky test ClientIdQuota #18612
Open
Conversation
This file contains 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
github-actions
bot
added
triage
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.
Jira: https://issues.apache.org/jira/browse/KAFKA-18568
The main reason is #18080 this commit modify the
linger.msconfig from 0 to 5, and these test are testing about "Low enough quota that a producer sending a small payload in a tight loop should get throttled", thus this config will Influence these test scenario.testing in my local with command
I=0; while ./gradlew :core:test --tests "kafka.api.ClientIdQuotaTest" --tests "kafka.api.UserClientIdQuotaTest" --tests "kafka.api.UserQuotaTest"--rerun --fail-fast; do (( I=$I+1 )); echo "Completed run: $I"; sleep 1; doneCommitter Checklist (excluded from commit message)