You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2016/01/20 19:27:40 UTC
[jira] [Assigned] (CASSANDRA-10905)
secondary_indexes_test.py:TestSecondaryIndexes.test_only_coordinator_chooses_index_for_query
flaps on 3.0+
[ https://issues.apache.org/jira/browse/CASSANDRA-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe reassigned CASSANDRA-10905:
-------------------------------------------
Assignee: Sam Tunnicliffe (was: DS Test Eng)
> secondary_indexes_test.py:TestSecondaryIndexes.test_only_coordinator_chooses_index_for_query flaps on 3.0+
> ----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10905
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Jim Witschey
> Assignee: Sam Tunnicliffe
> Fix For: 3.0.x
>
>
> This test flaps when it expects to find 1 of each of several trace events, but doesn't find some of them. I noticed it on 3.0:
> http://cassci.datastax.com/job/cassandra-3.0_dtest/438/testReport/junit/secondary_indexes_test/TestSecondaryIndexes/test_only_coordinator_chooses_index_for_query/history/
> But I've also seen it on trunk, so it would appear it hasn't been fixed:
> http://cassci.datastax.com/job/trunk_dtest/831/testReport/junit/secondary_indexes_test/TestSecondaryIndexes/test_only_coordinator_chooses_index_for_query/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)