Hey all,
MirrorConnectorsIntegration*Test#testOffsetTranslationBehindReplicationFlow()
flakiness should be addressed by
https://github.com/apache/kafka/pull/14156 which is currently in
review. There is other flakiness in the suite which this PR does not
address and needs further investigation.
Th
Here are some useful links for filtering failing tests by branches:
All branches:
https://ge.apache.org/scans/tests?search.rootProjectNames=kafka&search.relativeStartTime=P28D
trunk-only:
https://ge.apache.org/scans/tests?search.rootProjectNames=kafka&search.relativeStartTime=P28D&search.names=
Thanks Kirk!
I will try to go through in the next day or so and see if there is any
tests I can fix.
On Tue, Aug 8, 2023 at 3:13 PM Kirk True wrote:
> Hi Justine,
>
> > On Aug 1, 2023, at 4:50 PM, Justine Olshan
> wrote:
> >
> > Is that right that the first one on the list (
> >
> org.apache.ka
Hi Justine,
> On Aug 1, 2023, at 4:50 PM, Justine Olshan
> wrote:
>
> Is that right that the first one on the list (
> org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationExactlyOnceTest)
> takes
> 20 minutes?! That's quite a test.
> I wonder if the length corresponds to whet
Is that right that the first one on the list (
org.apache.kafka.connect.mirror.integration.MirrorConnectorsIntegrationExactlyOnceTest)
takes
20 minutes?! That's quite a test.
I wonder if the length corresponds to whether it passes, but we should fix
it and maybe move it out of our PR builds.
I was
Hi!
According to the Gradle Enterprise statistics on our recent Kafka builds, over
90% have flaky tests [1].
We also have 106 open Jiras with the “flaky-test” label across several
functional areas of the project [2].
Can I ask that those familiar with those different functional areas take a lo
