cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andres de la Peña (Jira) <>
Subject [jira] [Commented] (CASSANDRA-16621) Replace spinAsserts code with Awaitility code
Date Mon, 19 Jul 2021 16:26:00 GMT


Andres de la Peña commented on CASSANDRA-16621:

Here are some additional runs with LOWRES and HIGHRES:


I have added some multiplexed runs {{ViewFilteringTest}} because it's one the tests failing
with the {{ProtocolError}}/{{AlreadyExistsException}} errors, although I'm not finding them

What seems to be consistently failing due to the changes is {{ThreadPoolMetricsTest}}. The
failure seems to be caused by the increased poll interval. We could reduce it again, but it
might be better to directly use {{Awaitility}} in {{ThreadPoolMetricsTest.spinAssertEquals}}
with a lower interval or, even better, try to use a better concurrency control in the test.

> Replace spinAsserts code with Awaitility code
> ---------------------------------------------
>                 Key: CASSANDRA-16621
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message