Thanks Jiajun I agree with your proposal 100%. I don’t have the access to close the bugs and so will need commiters help. I can provide you with the list as that’s what I am currently doing and remaining ones, will assign others.
Will you be ok, if I provide with link of bugs which needs to be closed (lack of logs or no update for last 6 months) Thanks, Komal From: Wang Jiajun <[email protected]> Date: Wednesday, May 31, 2023 at 10:16 AM To: [email protected] <[email protected]>, Komal Desai <[email protected]> Subject: Re: Old FailedTests Here's what I proposed in the old days: 1. Close any test unstable ticket if there is no update in the past 4-6 months. 2. Assign test failure tickets to individuals with capacity or whoever want to contribute. Treat the tickets as KTLO tickets, set up ETA and keep tracking. Unfortunately, there is no easy way to fix test cases in a short time, we have to look into every ticket one by one. Best Regards, Jiajun On Wed, May 31, 2023 at 6:45 AM Komal Desai via user <[email protected]<mailto:[email protected]>> wrote: Hello Helix community Currently we have 99 failed test cases. https://github.com/apache/helix/issues?q=is%3Aissue+is%3Aopen+label%3AFailedTestTracking+sort%3Acomments-desc But many of the test failures don’t even have logs to debug. For example: https://github.com/apache/helix/issues/2197 Can you please suggest how we can make progress? Should we go through and close those old bugs with no logs available? Thanks, Komal (Helix dev – LinkedIn)
