[
https://issues.apache.org/jira/browse/KAFKA-9585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913064#comment-17913064
]
Lianet Magrans commented on KAFKA-9585:
---------------------------------------
Reopening as I got this flaky test in a recent build
[https://github.com/apache/kafka/actions/runs/12772513547/job/35602650058?pr=18533]
, (failing with a different msg)
java.lang.AssertionError: Expected: <0L> but: was <5L> at
org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) at
org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:6) at
org.apache.kafka.streams.integration.LagFetchIntegrationTest.shouldFetchLagsDuringRebalancing(LagFetchIntegrationTest.java:228)
at
org.apache.kafka.streams.integration.LagFetchIntegrationTest.shouldFetchLagsDuringRebalancingWithOptimization(LagFetchIntegrationTest.java:247)
Seemed convenient to just reopen this as tracker for the flaky test, but happy
to create a new Jira if we prefer.
> Flaky Test:
> LagFetchIntegrationTest#shouldFetchLagsDuringRebalancingWithOptimization
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-9585
> URL: https://issues.apache.org/jira/browse/KAFKA-9585
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 2.6.0
> Reporter: A. Sophie Blee-Goldman
> Priority: Major
> Labels: flaky-test
>
> Failed for me locally with
> {noformat}
> java.lang.AssertionError: Condition not met within timeout 120000. Should
> obtain non-empty lag information eventually
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
