Ability to close issues ?

[Komal Desai <ko...@gmail.com>]

Hello,

I am wondering how I can clean up the bug backlog of Apache Helix?
Currently there are 279 open issues and very hard to prioritize the top
bugs.

I see multiple duplicate bugs,
eg: https://github.com/apache/helix/issues/2414
and
https://github.com/apache/helix/issues/2193

Both are for:
[Failed CI Test]
afterClass(org.apache.helix.integration.multizk.TestMultiZkConnectionConfig)

Please let me know how I can get the required access to close the bugs.

Process - improvements??

[Komal Desai <ko...@gmail.com>]

With the latest changes to Gitlab, we have to wait for committee members to
approve our review request to go through PR-CI.

Is it possible to revert or do something, so that for each iteration of
code review, we don't require to wait ?

Within LinkedIn, we have only 2 members who are on committee and others are
not yet. Can we publish the guidelines on what it takes for a member to
become part of an elite committee?

thanks,
Komal (LinkedIn - Helix)

Re: Ability to close issues ?

[Junkai Xue <jx...@apache.org>]

For duplication, as you mentioned before, that's the failure of the main
branch and metaclient branch.

When you have a fix to the issue and checkedin, the issue will be
automatically closed. Without commit, only committers have the privilege to
close the bug directly.

Or you can list out all old tickets. We can help to close the outdated ones.

Best,

Junkai

On Sat, Apr 8, 2023 at 3:14 PM Komal Desai <ko...@gmail.com> wrote:

> I am all for reducing CI failures. That's why my focus is on trying to
> fix. But there is too much noise too.
> I don't have the right access to close old bugs. but i am willing to
> update them with latest runs and close it.
>
> regards,
> komal
>
> On Sat, Apr 8, 2023 at 2:04 PM Wang Jiajun <er...@gmail.com> wrote:
>
>> Please feel free to close the test failure tickets if there has been no
>> update for more than 4-6 months.
>> But for the other tickets and test failure tickets that are still
>> "active", we should prioritize carefully. I notice Helix CI is always
>> failing recently and this aligns with the test failure tickets update here.
>> So I would strongly prefer resolving the problem and the tickets will go
>> away with time.
>>
>> Best Regards,
>> Jiajun
>>
>>
>> On Sat, Apr 8, 2023 at 1:26 PM Junkai Xue <ju...@gmail.com> wrote:
>>
>>> Unfortunately, it won’t be able to “clean” up with closing the ticket.
>>> Those tickets are auto generated when CI failed.
>>>
>>> The right way to avoid these kind of tickets is fixing the unstable
>>> tests.
>>>
>>> thanks,
>>> Junkai
>>>
>>> On Apr 8, 2023, at 12:56 PM, Komal Desai <ko...@gmail.com> wrote:
>>>
>>> 
>>> Hello,
>>>
>>> I am wondering how I can clean up the bug backlog of Apache Helix?
>>> Currently there are 279 open issues and very hard to prioritize the top
>>> bugs.
>>>
>>> I see multiple duplicate bugs,
>>> eg: https://github.com/apache/helix/issues/2414
>>> and
>>> https://github.com/apache/helix/issues/2193
>>>
>>> Both are for:
>>> [Failed CI Test]
>>> afterClass(org.apache.helix.integration.multizk.TestMultiZkConnectionConfig)
>>>
>>> Please let me know how I can get the required access to close the bugs.
>>>
>>>

Re: Ability to close issues ?

[Komal Desai <ko...@gmail.com>]

I am all for reducing CI failures. That's why my focus is on trying to fix.
But there is too much noise too.
I don't have the right access to close old bugs. but i am willing to update
them with latest runs and close it.

regards,
komal

On Sat, Apr 8, 2023 at 2:04 PM Wang Jiajun <er...@gmail.com> wrote:

> Please feel free to close the test failure tickets if there has been no
> update for more than 4-6 months.
> But for the other tickets and test failure tickets that are still
> "active", we should prioritize carefully. I notice Helix CI is always
> failing recently and this aligns with the test failure tickets update here.
> So I would strongly prefer resolving the problem and the tickets will go
> away with time.
>
> Best Regards,
> Jiajun
>
>
> On Sat, Apr 8, 2023 at 1:26 PM Junkai Xue <ju...@gmail.com> wrote:
>
>> Unfortunately, it won’t be able to “clean” up with closing the ticket.
>> Those tickets are auto generated when CI failed.
>>
>> The right way to avoid these kind of tickets is fixing the unstable tests.
>>
>> thanks,
>> Junkai
>>
>> On Apr 8, 2023, at 12:56 PM, Komal Desai <ko...@gmail.com> wrote:
>>
>> 
>> Hello,
>>
>> I am wondering how I can clean up the bug backlog of Apache Helix?
>> Currently there are 279 open issues and very hard to prioritize the top
>> bugs.
>>
>> I see multiple duplicate bugs,
>> eg: https://github.com/apache/helix/issues/2414
>> and
>> https://github.com/apache/helix/issues/2193
>>
>> Both are for:
>> [Failed CI Test]
>> afterClass(org.apache.helix.integration.multizk.TestMultiZkConnectionConfig)
>>
>> Please let me know how I can get the required access to close the bugs.
>>
>>

Re: Ability to close issues ?

[Wang Jiajun <er...@gmail.com>]

Please feel free to close the test failure tickets if there has been no
update for more than 4-6 months.
But for the other tickets and test failure tickets that are still "active",
we should prioritize carefully. I notice Helix CI is always failing
recently and this aligns with the test failure tickets update here. So I
would strongly prefer resolving the problem and the tickets will go away
with time.

Best Regards,
Jiajun


On Sat, Apr 8, 2023 at 1:26 PM Junkai Xue <ju...@gmail.com> wrote:

> Unfortunately, it won’t be able to “clean” up with closing the ticket.
> Those tickets are auto generated when CI failed.
>
> The right way to avoid these kind of tickets is fixing the unstable tests.
>
> thanks,
> Junkai
>
> On Apr 8, 2023, at 12:56 PM, Komal Desai <ko...@gmail.com> wrote:
>
> 
> Hello,
>
> I am wondering how I can clean up the bug backlog of Apache Helix?
> Currently there are 279 open issues and very hard to prioritize the top
> bugs.
>
> I see multiple duplicate bugs,
> eg: https://github.com/apache/helix/issues/2414
> and
> https://github.com/apache/helix/issues/2193
>
> Both are for:
> [Failed CI Test]
> afterClass(org.apache.helix.integration.multizk.TestMultiZkConnectionConfig)
>
> Please let me know how I can get the required access to close the bugs.
>
>

Re: Ability to close issues ?

[Junkai Xue <ju...@gmail.com>]

Unfortunately, it won’t be able to “clean” up with closing the ticket. Those tickets are auto generated when CI failed.

The right way to avoid these kind of tickets is fixing the unstable tests.

thanks,
Junkai

> On Apr 8, 2023, at 12:56 PM, Komal Desai <ko...@gmail.com> wrote:
> 
> 
> Hello,
> 
> I am wondering how I can clean up the bug backlog of Apache Helix?
> Currently there are 279 open issues and very hard to prioritize the top bugs.
> 
> I see multiple duplicate bugs, 
> eg: https://github.com/apache/helix/issues/2414
> and
> https://github.com/apache/helix/issues/2193
> 
> Both are for:
> [Failed CI Test] afterClass(org.apache.helix.integration.multizk.TestMultiZkConnectionConfig)
> 
> Please let me know how I can get the required access to close the bugs.
>