[
https://issues.apache.org/jira/browse/KAFKA-16024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032832#comment-18032832
]
Kirk True commented on KAFKA-16024:
-----------------------------------
Per KAFKA-7605, this test has been flaky since 2018, so it's not specific to
the "new" consumer.
Per
[Develocity|https://develocity.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=kafka&search.timeZoneId=America%2FLos_Angeles&tests.container=kafka.api.SaslSslConsumerTest],
it's flaky for the {{SaslSslConsumerTest}} version of the test, too.
I have to run many iterations of the test to see it fail:
{code:bash}
COUNT=500
for ((i=1; i<=$COUNT; i++)); do
./gradlew -q \
:core:test \
--tests "kafka.api.SaslSslConsumerTest.testCoordinatorFailover" \
--rerun \
--fail-fast \
-x spotbugsMain \
-x spotbugsTest \
-x checkstyleMain \
-x checkstyleTest
echo "Completed run: $i"
sleep 1
done
{code}
> SaslPlaintextConsumerTest#testCoordinatorFailover is flaky
> ----------------------------------------------------------
>
> Key: KAFKA-16024
> URL: https://issues.apache.org/jira/browse/KAFKA-16024
> Project: Kafka
> Issue Type: Test
> Components: clients, consumer
> Reporter: Philip Nee
> Assignee: Phuc Hong Tran
> Priority: Major
> Labels: flaky-test, integration-tests
> Fix For: 4.2.0
>
>
> The test is flaky with the async consumer as we are observing
>
> {code:java}
> org.opentest4j.AssertionFailedError: Failed to observe commit callback before
> timeout{code}
> I was not able to replicate this on my local machine easily.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
