[ https://issues.apache.org/jira/browse/KAFKA-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512290#comment-17512290 ]
Luke Chen edited comment on KAFKA-7957 at 3/25/22, 10:00 AM: ------------------------------------------------------------- We didn't put the latest failed error stack trace, which is not easy to investigate. Maybe we can re-enable it and gather the failed message when occurrence? was (Author: showuon): We didn't put the latest failed error stack trace, which is not easy to investigate > Flaky Test DynamicBrokerReconfigurationTest#testMetricsReporterUpdate > --------------------------------------------------------------------- > > Key: KAFKA-7957 > URL: https://issues.apache.org/jira/browse/KAFKA-7957 > Project: Kafka > Issue Type: Bug > Components: core, unit tests > Affects Versions: 2.2.0 > Reporter: Matthias J. Sax > Priority: Blocker > Labels: flaky-test > Fix For: 3.2.0 > > > To get stable nightly builds for `2.2` release, I create tickets for all > observed test failures. > [https://jenkins.confluent.io/job/apache-kafka-test/job/2.2/18/] > {quote}java.lang.AssertionError: Messages not sent at > kafka.utils.TestUtils$.fail(TestUtils.scala:356) at > kafka.utils.TestUtils$.waitUntilTrue(TestUtils.scala:766) at > kafka.server.DynamicBrokerReconfigurationTest.startProduceConsume(DynamicBrokerReconfigurationTest.scala:1270) > at > kafka.server.DynamicBrokerReconfigurationTest.testMetricsReporterUpdate(DynamicBrokerReconfigurationTest.scala:650){quote} -- This message was sent by Atlassian Jira (v8.20.1#820001)