gharris1727 commented on PR #16273:
URL: https://github.com/apache/kafka/pull/16273#issuecomment-2159746582
I still see some remaining flakiness in this test.
It fails ~10% of the time at 30% CPU, rising to ~70% of the time at 15% CPU.
The failures are mostly this one:
```
caught: org.apache.kafka.connect.errors.DataException: Insufficient records
committed by connector simple-connector in 300 millis. Records expected=8,
actual=0
at
org.apache.kafka.connect.integration.ConnectorHandle.awaitCommits(ConnectorHandle.java:213)
at
org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testReconfigureConnectorWithFailingTaskConfigs(ConnectWorkerIntegrationTest.java:1292)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
```
with a handful of these two:
```
caught: java.lang.AssertionError: Connector tasks were not restarted in time
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.assertTrue(Assert.java:42)
at
org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testReconfigureConnectorWithFailingTaskConfigs(ConnectWorkerIntegrationTest.java:1310)
```
```
caught: org.apache.kafka.connect.errors.DataException: Insufficient records
committed by connector simple-connector in 300 millis. Records expected=1,
actual=0
at
org.apache.kafka.connect.integration.ConnectorHandle.awaitCommits(ConnectorHandle.java:213)
at
org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testReconfigureConnectorWithFailingTaskConfigs(ConnectWorkerIntegrationTest.java:1317)
```
I'll look into this more tomorrow if you need some more info.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
