Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-13 Thread Qiang Huang
+1. Flaky tests failures bother contributors a lot. Resolving flak test
failures can greatly improve development efficiency.

PengHui Li  于2022年8月13日周六 10:06写道:

> 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  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  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
> > >
> > >
> >
>


-- 
BR,
Qiang Huang


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-12 Thread PengHui Li
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  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  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
> >
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-12 Thread Lari Hotari
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  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
>
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-12 Thread PengHui Li
> BTW, seems this is a Classic Project[2], and the New Project[1] can
provide
more features than the Classic Project[2].

I think the non-classic project is only available for committers.
I have tried. The project will be created under the Apache organization.

Thanks,
Penghui

On Fri, Aug 12, 2022 at 2:05 PM Haiting Jiang 
wrote:

> +1. Good idea.
>
> Thanks,
> Haiting
>
>
> On Thu, Aug 11, 2022 at 10:44 PM Max Xu  wrote:
>
> > +1 It would be awesome to utilize the GitHub Project to track issues.
> >
> > BTW, seems this is a Classic Project[2], and the New Project[1] can
> provide
> > more features than the Classic Project[2].
> >
> > [1] https://github.com/apache/pulsar/projects?type=new
> > [2] https://github.com/apache/pulsar/projects?type=classic
> >
> >
> > Best,
> > Max Xu
> >
> >
> > On Thu, Aug 11, 2022 at 11:26 AM Zixuan Liu  wrote:
> >
> > > +1
> > >
> > > Thanks,
> > > Zixuan
> > >
> > > Anon Hxy  于2022年8月11日周四 10:26写道:
> > >
> > > > +1
> > > > Good idea. We are on the way making CI more robust
> > > >
> > > > Thanks,
> > > > Xiaoyu Hou
> > > >
> > > > PengHui Li  于2022年8月10日周三 16:35写道:
> > > >
> > > > > 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
> > > > >
> > > > >
> > > >
> > >
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-12 Thread Haiting Jiang
+1. Good idea.

Thanks,
Haiting


On Thu, Aug 11, 2022 at 10:44 PM Max Xu  wrote:

> +1 It would be awesome to utilize the GitHub Project to track issues.
>
> BTW, seems this is a Classic Project[2], and the New Project[1] can provide
> more features than the Classic Project[2].
>
> [1] https://github.com/apache/pulsar/projects?type=new
> [2] https://github.com/apache/pulsar/projects?type=classic
>
>
> Best,
> Max Xu
>
>
> On Thu, Aug 11, 2022 at 11:26 AM Zixuan Liu  wrote:
>
> > +1
> >
> > Thanks,
> > Zixuan
> >
> > Anon Hxy  于2022年8月11日周四 10:26写道:
> >
> > > +1
> > > Good idea. We are on the way making CI more robust
> > >
> > > Thanks,
> > > Xiaoyu Hou
> > >
> > > PengHui Li  于2022年8月10日周三 16:35写道:
> > >
> > > > 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
> > > >
> > > >
> > >
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-11 Thread Max Xu
+1 It would be awesome to utilize the GitHub Project to track issues.

BTW, seems this is a Classic Project[2], and the New Project[1] can provide
more features than the Classic Project[2].

[1] https://github.com/apache/pulsar/projects?type=new
[2] https://github.com/apache/pulsar/projects?type=classic


Best,
Max Xu


On Thu, Aug 11, 2022 at 11:26 AM Zixuan Liu  wrote:

> +1
>
> Thanks,
> Zixuan
>
> Anon Hxy  于2022年8月11日周四 10:26写道:
>
> > +1
> > Good idea. We are on the way making CI more robust
> >
> > Thanks,
> > Xiaoyu Hou
> >
> > PengHui Li  于2022年8月10日周三 16:35写道:
> >
> > > 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
> > >
> > >
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread Zixuan Liu
+1

Thanks,
Zixuan

Anon Hxy  于2022年8月11日周四 10:26写道:

> +1
> Good idea. We are on the way making CI more robust
>
> Thanks,
> Xiaoyu Hou
>
> PengHui Li  于2022年8月10日周三 16:35写道:
>
> > 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
> >
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread Anon Hxy
+1
Good idea. We are on the way making CI more robust

Thanks,
Xiaoyu Hou

PengHui Li  于2022年8月10日周三 16:35写道:

> 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
>
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread Michael Marshall
+1 Great idea!

Thanks,
Michael

On Wed, Aug 10, 2022 at 9:52 AM Yunze Xu  wrote:
>
> +1. Though the image url is broken :(
>
> Thanks,
> Yunze
>
>
>
>
> > 2022年8月10日 16:35,PengHui Li  写道:
> >
> > 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.
> >
> >
> > Best,
> > Penghui
> >
>


Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread Yunze Xu
+1. Though the image url is broken :(

Thanks,
Yunze




> 2022年8月10日 16:35,PengHui Li  写道:
> 
> 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.
> 
> 
> Best,
> Penghui
> 



Re: [DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread Yubiao Feng
That is a good way to track flaky test fix

+1

On Wed, Aug 10, 2022 at 4:35 PM PengHui Li  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
>
>


[DISCUSS] Create a new Github Project to track the flaky tests

2022-08-10 Thread PengHui Li
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