+1 to Mick's points.
Also notice in circle 4.1 green runs are the norm lately imo. Yes it's
not the official CI but it helps build an overall picture of improvement
towards green CI. On jenkins, if you check the latest 4.1 runs, <5-ish
failures per run are starting to be common and those that don't are
known failures being worked on (CAS i.e.), infra or flakies taking you
back to the <5-ish failures. So overall, if I am not missing anything,
the signal among the infra and flaky noise is pretty good.
Regards
On 17/8/22 22:50, Ekaterina Dimitrova wrote:
+1, I second Mick on both points.
On Wed, 17 Aug 2022 at 16:23, Mick Semb Wever <m...@apache.org> wrote:
We're down from 13 tickets blocking 4.1 beta down to 7:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2455
<https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484&quickFilter=2455>.
As mentioned above, we have some test failures w/out tickets
so that 7 is probably closer realistically to the previous count.
I suggest we move to beta when all non-flaky-test tickets are
resolved and we get our first green ci-cassandra run.
And I suggest we move to rc when we get three consecutive green runs.
We did something similar last time, this would be the same
exception to the rules, rules we continue to get closer to.
An alternative is to replace "green" with "builds with only
non-regression and infra-caused failures".
- It's pretty expensive and painful to defer cleaning up CI to
the end of the release cycle
This^
