You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@helix.apache.org by Komal Desai via user <us...@helix.apache.org> on 2023/05/31 23:32:29 UTC
Close bugs
Each bug has a date next to it which indicates last time the failure was observed.
1. https://github.com/apache/helix/pull/2142 (we bumped up to 4.5.14 recently.
2. https://github.com/apache/helix/issues/1768 - aug 6 2021 (Jiajun had already fixed but it was reopened)
3. https://github.com/apache/helix/issues/1780 - sept 2021<https://github.com/apache/helix/issues/1780%20-%20sept%202021>
4. https://github.com/apache/helix/issues/1786 - Sept 2021 (Fix was checked in)
5. https://github.com/apache/helix/issues/1788 - Aug 2021 (Fixed by Jiajun)
6. https://github.com/apache/helix/issues/1808 Aug 2021 (assigned to Xiaoyuan)
7. https://github.com/apache/helix/issues/1814 - July 2021<https://github.com/apache/helix/issues/1814%20-%20July%202021>
8. https://github.com/apache/helix/issues/1826 - Oct 2021<https://github.com/apache/helix/issues/1826%20-%20Oct%202021>
9. https://github.com/apache/helix/issues/1830 - Oct 2021<https://github.com/apache/helix/issues/1830%20-%20Oct%202021>
10. https://github.com/apache/helix/issues/1837 - Nov 2021<https://github.com/apache/helix/issues/1837%20-%20Nov%202021>
There are many but in batch of 10s for manageable actions. The date next to each bug is the last time the test failed.
I am sorry to bother but this is required to make sure backlog healthy and manageable. Apache Helix commiters pleae help. There may be additional 2 or 3 such emails.
Thanks,
Komal (Helix Dev)
From: Komal Desai <kd...@linkedin.com>
Date: Wednesday, May 31, 2023 at 10:20 AM
To: Wang Jiajun <er...@gmail.com>, user@helix.apache.org <us...@helix.apache.org>
Subject: Re: Old FailedTests
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 <er...@gmail.com>
Date: Wednesday, May 31, 2023 at 10:16 AM
To: user@helix.apache.org <us...@helix.apache.org>, Komal Desai <kd...@linkedin.com>
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 <us...@helix.apache.org>> 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)
Re: Close bugs
Posted by Komal Desai via user <us...@helix.apache.org>.
THANKS A LOT. There may be 2 to 3 such emails, and hopefully we will get handle on others. Thanks once again.
komal
From: Wang Jiajun <er...@gmail.com>
Date: Wednesday, May 31, 2023 at 5:21 PM
To: user@helix.apache.org <us...@helix.apache.org>, Komal Desai <kd...@linkedin.com>
Subject: Re: Close bugs
Done : )
Best Regards,
Jiajun
On Wed, May 31, 2023 at 4:32 PM Komal Desai via user <us...@helix.apache.org>> wrote:
Each bug has a date next to it which indicates last time the failure was observed.
1. https://github.com/apache/helix/pull/2142 (we bumped up to 4.5.14 recently.
2. https://github.com/apache/helix/issues/1768 - aug 6 2021 (Jiajun had already fixed but it was reopened)
3. https://github.com/apache/helix/issues/1780 - sept 2021<https://github.com/apache/helix/issues/1780%20-%20sept%202021>
4. https://github.com/apache/helix/issues/1786 - Sept 2021 (Fix was checked in)
5. https://github.com/apache/helix/issues/1788 - Aug 2021 (Fixed by Jiajun)
6. https://github.com/apache/helix/issues/1808 Aug 2021 (assigned to Xiaoyuan)
7. https://github.com/apache/helix/issues/1814 - July 2021<https://github.com/apache/helix/issues/1814%20-%20July%202021>
8. https://github.com/apache/helix/issues/1826 - Oct 2021<https://github.com/apache/helix/issues/1826%20-%20Oct%202021>
9. https://github.com/apache/helix/issues/1830 - Oct 2021<https://github.com/apache/helix/issues/1830%20-%20Oct%202021>
10. https://github.com/apache/helix/issues/1837 - Nov 2021<https://github.com/apache/helix/issues/1837%20-%20Nov%202021>
There are many but in batch of 10s for manageable actions. The date next to each bug is the last time the test failed.
I am sorry to bother but this is required to make sure backlog healthy and manageable. Apache Helix commiters pleae help. There may be additional 2 or 3 such emails.
Thanks,
Komal (Helix Dev)
From: Komal Desai <kd...@linkedin.com>>
Date: Wednesday, May 31, 2023 at 10:20 AM
To: Wang Jiajun <er...@gmail.com>>, user@helix.apache.org<ma...@helix.apache.org> <us...@helix.apache.org>>
Subject: Re: Old FailedTests
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 <er...@gmail.com>>
Date: Wednesday, May 31, 2023 at 10:16 AM
To: user@helix.apache.org<ma...@helix.apache.org> <us...@helix.apache.org>>, Komal Desai <kd...@linkedin.com>>
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 <us...@helix.apache.org>> 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)
Re: Close bugs
Posted by Wang Jiajun <er...@gmail.com>.
Done : )
Best Regards,
Jiajun
On Wed, May 31, 2023 at 4:32 PM Komal Desai via user <us...@helix.apache.org>
wrote:
> Each bug has a date next to it which indicates last time the failure was
> observed.
>
>
>
> 1. https://github.com/apache/helix/pull/2142 (we bumped up to 4.5.14
> recently.
> 2. https://github.com/apache/helix/issues/1768 - aug 6 2021 (Jiajun
> had already fixed but it was reopened)
> 3. https://github.com/apache/helix/issues/1780 - sept 2021
> 4. https://github.com/apache/helix/issues/1786 - Sept 2021 (Fix was
> checked in)
> 5. https://github.com/apache/helix/issues/1788 - Aug 2021 (Fixed by
> Jiajun)
> 6. https://github.com/apache/helix/issues/1808 Aug 2021 (assigned to
> Xiaoyuan)
> 7. https://github.com/apache/helix/issues/1814 - July 2021
> 8. https://github.com/apache/helix/issues/1826 - Oct 2021
> 9. https://github.com/apache/helix/issues/1830 - Oct 2021
> 10. https://github.com/apache/helix/issues/1837 - Nov 2021
>
> There are many but in batch of 10s for manageable actions. The date next
> to each bug is the last time the test failed.
>
>
>
> I am sorry to bother but this is required to make sure backlog healthy and
> manageable. Apache Helix commiters pleae help. There may be additional 2 or
> 3 such emails.
>
>
>
> Thanks,
>
> Komal (Helix Dev)
>
>
>
> *From: *Komal Desai <kd...@linkedin.com>
> *Date: *Wednesday, May 31, 2023 at 10:20 AM
> *To: *Wang Jiajun <er...@gmail.com>, user@helix.apache.org <
> user@helix.apache.org>
> *Subject: *Re: Old FailedTests
>
> 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 <er...@gmail.com>
> *Date: *Wednesday, May 31, 2023 at 10:16 AM
> *To: *user@helix.apache.org <us...@helix.apache.org>, Komal Desai <
> kdesai@linkedin.com>
> *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 <
> user@helix.apache.org> 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)
>
>