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 also wondering if we could distinguish PR builds from trunk builds. That might give us a better signal since PR builds could be before tests are fixed. Not sure which one is being reported here. Thanks for sharing though! This is a useful tool that we've needed for a while. Justine On Tue, Aug 1, 2023 at 4:38 PM Kirk True <k...@kirktrue.pro> wrote: > 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 > look at the list of flaky tests and triage them? > > Thanks, > Kirk > > [1] > https://ge.apache.org/scans/tests?search.relativeStartTime=P28D&search.rootProjectNames=kafka > [2] > https://issues.apache.org/jira/issues/?jql=project%20%3D%20KAFKA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20labels%20%3D%20flaky-test
