cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11465) dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
Date Mon, 25 Jul 2016 05:39:20 GMT


Stefania commented on CASSANDRA-11465:

There's a static method that we won't be able to capture with futures but even the approach
based on adding a no op event could have the same race, see CASSANDRA-5668. Basically the
state may be deleted before the coordinator receives all responses or even sends all requests
but this is not applicable to CL.ALL. Also, the 3.9 patch becomes a little bit more involved
due to the abstractions introduced by CASSANDRA-10392.

Launched the tests again, the latest changes are in a separate commit so we can choose which
approach to use. I would prefer to use futures since it is more accurate.


Only the 2.2 and 3.9 commits need reviewing, the 3.0 and trunk commits are identical to the
2.2. and 3.9 commits respectively.

I've also created the pull request for dtests [here|].

> dtest failure in cql_tracing_test.TestCqlTracing.tracing_unknown_impl_test
> --------------------------------------------------------------------------
>                 Key: CASSANDRA-11465
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Philip Thompson
>            Assignee: Stefania
>              Labels: dtest
> Failing on the following assert, on trunk only: {{self.assertEqual(len(errs[0]), 1)}}
> Is not failing consistently.
> example failure:
> Failed on CassCI build trunk_dtest #1087

This message was sent by Atlassian JIRA

View raw message