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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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 <[email protected]> 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. >>> >>>
