> testAutoSnapshotTTIOnDropAfterRestart has failed a few times so there's some legit flake there: https://ci-cassandra.apache.org/job/Cassandra-4.1/138/testReport/org.apache.cassandra.distributed.test/AutoSnapshotTtlTest/testAutoSnapshotTTlOnDropAfterRestart_2/. No build lead lately so we don't have a JIRA for it or associated with it ( https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=496&quickFilter=2252); I may put that mantle back on in the near future.
There's https://issues.apache.org/jira/browse/CASSANDRA-17804, for some reason it's not showing up in the kanban board.. Em qua., 17 de ago. de 2022 às 17:24, Mick Semb Wever <m...@apache.org> escreveu: > 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. >> 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^ >
