You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Nicolò Boschi <bo...@gmail.com> on 2023/02/07 15:43:02 UTC
Pulsar Flaky test report 2023-02-07 for PR builds in CI
Dear community,
Here's a report of the flaky tests in Pulsar CI during the observation
period of 2023-01-31 - 2023-02-07
https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07
More flaky test issues:
https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+is%3Aopen+is:issue
To coordinate the work,
1) please search for an existing issues or search for all flaky issues with
"flaky" or the test class name (without package) in the search:
https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
2) If there isn't an issue for a particular flaky test failure that you'd
like to fix, please create an issue using the "Flaky test" template at
https://github.com/apache/pulsar/issues/new/choose
3) Please comment on the issue that you are working on.
I'm looking forward to more contributors joining the efforts. Please join
the #testing channel on Slack if you'd like to ask questions and tips about
reproducing flaky tests locally and how to fix them.
Sharing stories about fixing flaky tests is also helpful for sharing the
knowledge about how flaky tests can be fixed. That's also a valuable way to
contribute.
Some flaky tests might be actual real production code bugs. Fixing
the flaky test might result in fixing a real production code bug.
More contributions are welcome! Please keep up the good work!
P.S.
The flaky test reporter was originally coded by Lari. Lately, we simplified
the way to generate the report to allow more people to access the report
and for scheduling purpose.
There are instructions on how to generate it here:
https://github.com/nicoloboschi/pulsar-flakes#generate-a-new-report
Thanks,
Nicolò Boschi
Re: Pulsar Flaky test report 2023-02-07 for PR builds in CI
Posted by Yubiao Feng <yu...@streamnative.io.INVALID>.
Thanks, very useful +1.
Yubiao Feng
On Fri, Feb 10, 2023 at 5:45 AM Lari Hotari <lh...@apache.org> wrote:
> Thanks, very useful.
>
> -Lari
>
> On 2023/02/09 15:24:28 Nicolò Boschi wrote:
> > Sorry I haven't linked the google sheet:
> >
> https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit#gid=1022097898
> >
> >
> > The most relevant are:
> >
> org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved
> > 42 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved+testDeleteUselessLogDataWhenSubCursorMoved
> >
> >
> org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost
> > 23 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLeadershipAfterSessionLost+testReacquireLeadershipAfterSessionLost
> >
> >
> org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost
> > 19 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLocksAfterSessionLost+testReacquireLocksAfterSessionLost
> >
> >
> org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer
> > 19 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer+testAddRemoveConsumer
> >
> >
> org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer
> > 11 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer+testAddRemoveConsumer
> >
> >
> org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats
> > 9 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=MetadataStoreStatsTest.testMetadataStoreStats+testMetadataStoreStats
> >
> >
> org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource
> > 9 Detailed report
> > <
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource.md
> >
> > Search
> > issues
> > <
> https://github.com/apache/pulsar/issues?q=PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource+testDebeziumOracleDbSource
> >
> >
> > PendingAckPersistentTest and MetadataStoreStatsTest are already fixed.
> > The other ones already have an issue and they're long standing flaky
> tests
> >
> >
> > Nicolò Boschi
> >
> >
> > Il giorno mar 7 feb 2023 alle ore 22:44 Lari Hotari <lh...@apache.org>
> ha
> > scritto:
> >
> > > Thanks for compiling the report Nicolo.
> > >
> > > What are the 10 most flaky tests? It wasn't obvious to me from the
> email.
> > > I'd like to suggest that we prioritize fixing the 10 most flaky ones.
> > >
> > > -Lari
> > >
> > > ti 7. helmik. 2023 klo 17.43 Nicolò Boschi <bo...@gmail.com>
> > > kirjoitti:
> > >
> > > > Dear community,
> > > > Here's a report of the flaky tests in Pulsar CI during the
> observation
> > > > period of 2023-01-31 - 2023-02-07
> > > >
> > > >
> > > >
> > >
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07
> > > >
> > > > More flaky test issues:
> > > >
> > > >
> > >
> https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+is%3Aopen+is:issue
> > > >
> > > >
> > > > To coordinate the work,
> > > > 1) please search for an existing issues or search for all flaky
> issues
> > > with
> > > > "flaky" or the test class name (without package) in the search:
> > > >
> > > >
> > >
> https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
> > > > 2) If there isn't an issue for a particular flaky test failure that
> you'd
> > > > like to fix, please create an issue using the "Flaky test" template
> at
> > > > https://github.com/apache/pulsar/issues/new/choose
> > > > 3) Please comment on the issue that you are working on.
> > > >
> > > > I'm looking forward to more contributors joining the efforts. Please
> join
> > > > the #testing channel on Slack if you'd like to ask questions and tips
> > > about
> > > > reproducing flaky tests locally and how to fix them.
> > > > Sharing stories about fixing flaky tests is also helpful for sharing
> the
> > > > knowledge about how flaky tests can be fixed. That's also a valuable
> way
> > > to
> > > > contribute.
> > > > Some flaky tests might be actual real production code bugs. Fixing
> > > > the flaky test might result in fixing a real production code bug.
> > > >
> > > > More contributions are welcome! Please keep up the good work!
> > > >
> > > > P.S.
> > > > The flaky test reporter was originally coded by Lari. Lately, we
> > > simplified
> > > > the way to generate the report to allow more people to access the
> report
> > > > and for scheduling purpose.
> > > > There are instructions on how to generate it here:
> > > > https://github.com/nicoloboschi/pulsar-flakes#generate-a-new-report
> > > >
> > > >
> > > > Thanks,
> > > > Nicolò Boschi
> > > >
> > >
> >
>
Re: Pulsar Flaky test report 2023-02-07 for PR builds in CI
Posted by Lari Hotari <lh...@apache.org>.
Thanks, very useful.
-Lari
On 2023/02/09 15:24:28 Nicolò Boschi wrote:
> Sorry I haven't linked the google sheet:
> https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit#gid=1022097898
>
>
> The most relevant are:
> org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved
> 42 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved+testDeleteUselessLogDataWhenSubCursorMoved>
> org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost
> 23 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLeadershipAfterSessionLost+testReacquireLeadershipAfterSessionLost>
> org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost
> 19 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLocksAfterSessionLost+testReacquireLocksAfterSessionLost>
> org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer
> 19 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer+testAddRemoveConsumer>
> org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer
> 11 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer+testAddRemoveConsumer>
> org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats
> 9 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=MetadataStoreStatsTest.testMetadataStoreStats+testMetadataStoreStats>
> org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource
> 9 Detailed report
> <https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource.md>
> Search
> issues
> <https://github.com/apache/pulsar/issues?q=PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource+testDebeziumOracleDbSource>
>
> PendingAckPersistentTest and MetadataStoreStatsTest are already fixed.
> The other ones already have an issue and they're long standing flaky tests
>
>
> Nicolò Boschi
>
>
> Il giorno mar 7 feb 2023 alle ore 22:44 Lari Hotari <lh...@apache.org> ha
> scritto:
>
> > Thanks for compiling the report Nicolo.
> >
> > What are the 10 most flaky tests? It wasn't obvious to me from the email.
> > I'd like to suggest that we prioritize fixing the 10 most flaky ones.
> >
> > -Lari
> >
> > ti 7. helmik. 2023 klo 17.43 Nicolò Boschi <bo...@gmail.com>
> > kirjoitti:
> >
> > > Dear community,
> > > Here's a report of the flaky tests in Pulsar CI during the observation
> > > period of 2023-01-31 - 2023-02-07
> > >
> > >
> > >
> > https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07
> > >
> > > More flaky test issues:
> > >
> > >
> > https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+is%3Aopen+is:issue
> > >
> > >
> > > To coordinate the work,
> > > 1) please search for an existing issues or search for all flaky issues
> > with
> > > "flaky" or the test class name (without package) in the search:
> > >
> > >
> > https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
> > > 2) If there isn't an issue for a particular flaky test failure that you'd
> > > like to fix, please create an issue using the "Flaky test" template at
> > > https://github.com/apache/pulsar/issues/new/choose
> > > 3) Please comment on the issue that you are working on.
> > >
> > > I'm looking forward to more contributors joining the efforts. Please join
> > > the #testing channel on Slack if you'd like to ask questions and tips
> > about
> > > reproducing flaky tests locally and how to fix them.
> > > Sharing stories about fixing flaky tests is also helpful for sharing the
> > > knowledge about how flaky tests can be fixed. That's also a valuable way
> > to
> > > contribute.
> > > Some flaky tests might be actual real production code bugs. Fixing
> > > the flaky test might result in fixing a real production code bug.
> > >
> > > More contributions are welcome! Please keep up the good work!
> > >
> > > P.S.
> > > The flaky test reporter was originally coded by Lari. Lately, we
> > simplified
> > > the way to generate the report to allow more people to access the report
> > > and for scheduling purpose.
> > > There are instructions on how to generate it here:
> > > https://github.com/nicoloboschi/pulsar-flakes#generate-a-new-report
> > >
> > >
> > > Thanks,
> > > Nicolò Boschi
> > >
> >
>
Re: Pulsar Flaky test report 2023-02-07 for PR builds in CI
Posted by Nicolò Boschi <bo...@gmail.com>.
Sorry I haven't linked the google sheet:
https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit#gid=1022097898
The most relevant are:
org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved
42 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.transaction.pendingack.PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=PendingAckPersistentTest.testDeleteUselessLogDataWhenSubCursorMoved+testDeleteUselessLogDataWhenSubCursorMoved>
org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost
23 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLeadershipAfterSessionLost.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLeadershipAfterSessionLost+testReacquireLeadershipAfterSessionLost>
org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost
19 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.metadata.ZKSessionTest.testReacquireLocksAfterSessionLost.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=ZKSessionTest.testReacquireLocksAfterSessionLost+testReacquireLocksAfterSessionLost>
org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer
19 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.persistent.PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerStreamingDispatcherTest.testAddRemoveConsumer+testAddRemoveConsumer>
org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer
11 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.service.PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=PersistentDispatcherFailoverConsumerTest.testAddRemoveConsumer+testAddRemoveConsumer>
org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats
9 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.broker.stats.MetadataStoreStatsTest.testMetadataStoreStats.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=MetadataStoreStatsTest.testMetadataStoreStats+testMetadataStoreStats>
org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource
9 Detailed report
<https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07/org.apache.pulsar.tests.integration.io.sources.debezium.PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource.md>
Search
issues
<https://github.com/apache/pulsar/issues?q=PulsarDebeziumOracleSourceTest.testDebeziumOracleDbSource+testDebeziumOracleDbSource>
PendingAckPersistentTest and MetadataStoreStatsTest are already fixed.
The other ones already have an issue and they're long standing flaky tests
Nicolò Boschi
Il giorno mar 7 feb 2023 alle ore 22:44 Lari Hotari <lh...@apache.org> ha
scritto:
> Thanks for compiling the report Nicolo.
>
> What are the 10 most flaky tests? It wasn't obvious to me from the email.
> I'd like to suggest that we prioritize fixing the 10 most flaky ones.
>
> -Lari
>
> ti 7. helmik. 2023 klo 17.43 Nicolò Boschi <bo...@gmail.com>
> kirjoitti:
>
> > Dear community,
> > Here's a report of the flaky tests in Pulsar CI during the observation
> > period of 2023-01-31 - 2023-02-07
> >
> >
> >
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07
> >
> > More flaky test issues:
> >
> >
> https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+is%3Aopen+is:issue
> >
> >
> > To coordinate the work,
> > 1) please search for an existing issues or search for all flaky issues
> with
> > "flaky" or the test class name (without package) in the search:
> >
> >
> https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
> > 2) If there isn't an issue for a particular flaky test failure that you'd
> > like to fix, please create an issue using the "Flaky test" template at
> > https://github.com/apache/pulsar/issues/new/choose
> > 3) Please comment on the issue that you are working on.
> >
> > I'm looking forward to more contributors joining the efforts. Please join
> > the #testing channel on Slack if you'd like to ask questions and tips
> about
> > reproducing flaky tests locally and how to fix them.
> > Sharing stories about fixing flaky tests is also helpful for sharing the
> > knowledge about how flaky tests can be fixed. That's also a valuable way
> to
> > contribute.
> > Some flaky tests might be actual real production code bugs. Fixing
> > the flaky test might result in fixing a real production code bug.
> >
> > More contributions are welcome! Please keep up the good work!
> >
> > P.S.
> > The flaky test reporter was originally coded by Lari. Lately, we
> simplified
> > the way to generate the report to allow more people to access the report
> > and for scheduling purpose.
> > There are instructions on how to generate it here:
> > https://github.com/nicoloboschi/pulsar-flakes#generate-a-new-report
> >
> >
> > Thanks,
> > Nicolò Boschi
> >
>
Re: Pulsar Flaky test report 2023-02-07 for PR builds in CI
Posted by Lari Hotari <lh...@apache.org>.
Thanks for compiling the report Nicolo.
What are the 10 most flaky tests? It wasn't obvious to me from the email.
I'd like to suggest that we prioritize fixing the 10 most flaky ones.
-Lari
ti 7. helmik. 2023 klo 17.43 Nicolò Boschi <bo...@gmail.com> kirjoitti:
> Dear community,
> Here's a report of the flaky tests in Pulsar CI during the observation
> period of 2023-01-31 - 2023-02-07
>
>
> https://github.com/nicoloboschi/pulsar-flakes/tree/master/2023-01-31-to-2023-02-07
>
> More flaky test issues:
>
> https://github.com/apache/pulsar/issues?q=flaky+sort%3Aupdated-desc+is%3Aopen+is:issue
>
>
> To coordinate the work,
> 1) please search for an existing issues or search for all flaky issues with
> "flaky" or the test class name (without package) in the search:
>
> https://github.com/apache/pulsar/issues?q=is%3Aopen+flaky+sort%3Aupdated-desc
> 2) If there isn't an issue for a particular flaky test failure that you'd
> like to fix, please create an issue using the "Flaky test" template at
> https://github.com/apache/pulsar/issues/new/choose
> 3) Please comment on the issue that you are working on.
>
> I'm looking forward to more contributors joining the efforts. Please join
> the #testing channel on Slack if you'd like to ask questions and tips about
> reproducing flaky tests locally and how to fix them.
> Sharing stories about fixing flaky tests is also helpful for sharing the
> knowledge about how flaky tests can be fixed. That's also a valuable way to
> contribute.
> Some flaky tests might be actual real production code bugs. Fixing
> the flaky test might result in fixing a real production code bug.
>
> More contributions are welcome! Please keep up the good work!
>
> P.S.
> The flaky test reporter was originally coded by Lari. Lately, we simplified
> the way to generate the report to allow more people to access the report
> and for scheduling purpose.
> There are instructions on how to generate it here:
> https://github.com/nicoloboschi/pulsar-flakes#generate-a-new-report
>
>
> Thanks,
> Nicolò Boschi
>