[
https://issues.apache.org/jira/browse/CASSANDRA-16621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383794#comment-17383794
]
Berenguer Blasi commented on CASSANDRA-16621:
---------------------------------------------
- +1 to {{ThreadPoolMetricsTest}} fixes
- +1 to the optimistic poll. Also the {{ConnectionTest}} should fail the test
case whereas it is timming out so that needs some tunning as well.
- The v4 protocol thing seems to be sthg that only happens to Jogesh. I need to
dig a bit more...
> 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]
