[ 
https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17381956#comment-17381956
 ] 

Berenguer Blasi commented on CASSANDRA-16621:
---------------------------------------------

I went for a 4.0 rebase and lgtm: 
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/381/workflows/0a811695-3a11-4ae1-94be-ef3c78fd0b88]
 & 
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/381/workflows/af3b3208-9b73-47cd-bf1a-b75b8c5ea9cf].
 {{ConnectionTest}} is a known offender so no worries there I would say.

You want to rebase and run 4.0 and trunk CI or do you prefer I do it for you 
while I am at it?

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to