[
https://issues.apache.org/jira/browse/KAFKA-12657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540423#comment-17540423
]
Chris Egerton commented on KAFKA-12657:
---------------------------------------
Giving it a shot with [https://github.com/apache/kafka/pull/12191.] I wish
there were a way to reduce parallelism with our tests since that seems to be
the root cause here, and (at least with my rudimentary laptop testing), it may
actually decrease the time for a complete test run. But for now, we can try
bumping timeouts and see if that stops the bleeding.
> Flaky Tests BlockingConnectorTest.testWorkerRestartWithBlockInConnectorStop
> ---------------------------------------------------------------------------
>
> Key: KAFKA-12657
> URL: https://issues.apache.org/jira/browse/KAFKA-12657
> Project: Kafka
> Issue Type: Test
> Components: KafkaConnect
> Reporter: Matthias J. Sax
> Priority: Critical
> Labels: flaky-test
>
> [https://github.com/apache/kafka/pull/10506/checks?check_run_id=2327377745]
> {quote} {{org.opentest4j.AssertionFailedError: Condition not met within
> timeout 60000. Worker did not complete startup in time ==> expected: <true>
> but was: <false>
> at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
> at org.junit.jupiter.api.AssertTrue.assertTrue(AssertTrue.java:40)
> at org.junit.jupiter.api.Assertions.assertTrue(Assertions.java:193)
> at
> org.apache.kafka.test.TestUtils.lambda$waitForCondition$3(TestUtils.java:319)
> at
> org.apache.kafka.test.TestUtils.retryOnExceptionWithTimeout(TestUtils.java:367)
> at org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:316)
> at org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:300)
> at org.apache.kafka.test.TestUtils.waitForCondition(TestUtils.java:290)
> at
> org.apache.kafka.connect.integration.BlockingConnectorTest.setup(BlockingConnectorTest.java:133)}}
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
