[
https://issues.apache.org/jira/browse/KAFKA-17395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875609#comment-17875609
]
Lianet Magrans commented on KAFKA-17395:
----------------------------------------
Hey [~taijuwu] / [~chia7712] , I noticed now that this test we enabled for the
new consumer has been flaky.
I'm currently working on a change to how fetch positions are updated in the
consumer ([https://github.com/apache/kafka/pull/16885]), that I wonder if it
could benefit this somehow? Honestly I don't know at this point, but just
sharing that we should review this flaky test with the new way of updating
fetch positions in mind (once that PR settles, I'm still actively changing)
> Flaky test testMissingOffsetNoResetPolicy for new consumer
> ----------------------------------------------------------
>
> Key: KAFKA-17395
> URL: https://issues.apache.org/jira/browse/KAFKA-17395
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Lianet Magrans
> Priority: Major
> Labels: consumer-threading-refactor
>
> KafkaConsumerTest.testMissingOffsetNoResetPolicy is flaky when running for
> the new consumer (passing consistently for the classic consumer).
> Fails with :
> org.opentest4j.AssertionFailedError: Condition not met within timeout 15000.
> Consumer was not able to update fetch positions on continuous calls with 0
> timeout ==> expected: <true> but was: <false>
> It's been flaky since it was enabled for the new consumer with
> [https://github.com/apache/kafka/pull/16587]
> See last couple of month runs on trunk showing the flakiness:
> [https://ge.apache.org/scans/tests?search.names=Git%20branch&search.rootProjectNames=kafka&search.startTimeMax=1724299199999&search.startTimeMin=1717214400000&search.timeZoneId=America%2FToronto&search.values=trunk&tests.container=org.apache.kafka.clients.consumer.KafkaConsumerTest&tests.test=testMissingOffsetNoResetPolicy(GroupProtocol)%5B2%5D]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
