First, I think we need to clarify if we're blocking on just testall + dtest or blocking on *all test jobs*.
If the latter, upgrade tests are the elephant in the room: http://cassci.datastax.com/view/cassandra-3.11/job/cassandra-3.11_dtest_upgrade/lastCompletedBuild/testReport/ Do we have confidence that the reported failures are all test problems and not w/Cassandra itself? If so, is that documented somewhere? On Mon, Jan 9, 2017 at 7:33 PM, Nate McCall <zznat...@gmail.com> wrote: > I'm not sure I understand the culmination of the past couple of threads on > this. > > With a situation like: > http://cassci.datastax.com/view/cassandra-3.11/job/cassandra-3.11_dtest/ > lastCompletedBuild/testReport/ > > We have some sense of stability on what might be flaky tests(?). > Again, I'm not sure what our criteria is specifically. > > Basically, it feels like we are in a stalemate right now. How do we > move forward? > > -Nate >
