I thought maybe we can close the flaky test with the Stale label. All of them are created very early and have no recurrence within a month. Maybe fixed by some PRs, but not sure about it.
Currently, I haven't added them to the Github Project. But still open in the Github issue list. Another one is the add-to-project CI does not work for classic projects. Lishen https://github.com/yaalsn is trying to improve the pulsar-test-infra to support adding issues/PRs to classic projects automatically. Best, Penghui On Sat, Aug 13, 2022 at 1:50 AM Lari Hotari <l...@hotari.net> wrote: > Thank you Penghui, really useful way to coordinate the fixing of flaky > tests! > > -Lari > > On Wed, Aug 10, 2022 at 11:35 AM PengHui Li <peng...@apache.org> wrote: > > > Hi all, > > > > For better tracking flaky test fix, I have tried to create a Github > > Project under the Pulsar repo > https://github.com/apache/pulsar/projects/11 > > (It can be removed if we don't like this way) > > This will help us to have a more intuitive view of all the flaky tests, > > how many are in progress, in the review stage, and approved. > > > > The project is public for all the contributors, so if you want > > to contribute some flaky tests fixes, > > you can go to the Github Project to peek up items in the Todo column. > > > > And I also created a PR https://github.com/apache/pulsar/pull/17038 to > > add the PRs and issues > > with `flaky-tests` label to this project automatically. > > > > BTW, I also have some questions about the Github Project automation. As > > the description of > > column `Review in progress, it said the PR with request changes would go > > to this column > > automatically. But it doesn't work. I'm not sure why. > > [image: image.png] > > > > Best, > > Penghui > > > > >
