[ https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382371#comment-17382371 ]
Jogesh Anand commented on CASSANDRA-16621: ------------------------------------------ That's nice. thanks! I would prefer to do it. Yeah, I did rebase the PR on 4.0. Also, updated the changes for trunk CI. ||branch || CI || |CI 4.0 || [j11|https://app.circleci.com/pipelines/github/djanand/cassandra/11/workflows/40ae1eb3-5292-4637-ac17-271cac1738e6] & [j8|https://app.circleci.com/pipelines/github/djanand/cassandra/11/workflows/a730dc81-11bb-413c-adaa-584ca9de8e37]| |CI trunk || [j11|https://app.circleci.com/pipelines/github/djanand/cassandra/12/workflows/abe8f0c5-f98d-448f-828a-092af41f02db] & [j8|https://app.circleci.com/pipelines/github/djanand/cassandra/12/workflows/abe8f0c5-f98d-448f-828a-092af41f02db]| Tracking both runs. I wonder what fixed the errors that we were getting earlier > 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