[ https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17377803#comment-17377803 ]
Berenguer Blasi commented on CASSANDRA-16621: --------------------------------------------- Run [#903|https://ci-cassandra.apache.org/job/Cassandra-devbranch/903/#showFailuresLink] failed on upgrade tests, which iirc was a thing a few days ago so it could be you only need a rebase. Atm we have 4.0 upgrade tests broken again since yesterday. I think we've just had unlucky timing. Let's wait for these to get fixed, I'll rebase then and re-run CI. > Replace spinAsserts code with Awaitility code > --------------------------------------------- > > Key: CASSANDRA-16621 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16621 > Project: Cassandra > Issue Type: Bug > Components: Test/unit > Reporter: Berenguer Blasi > Assignee: Jogesh Anand > Priority: Normal > Labels: low-hanging-fruit > Fix For: 4.0.x > > > Currently spinAsserts does a similar thing to Awaitility which is being used > more and more. We have now 2 ways of doing the same thing so it would be good > to consolidate -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org