You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jim Witschey (JIRA)" <ji...@apache.org> on 2015/09/11 19:06:48 UTC

[jira] [Created] (CASSANDRA-10308) Investigate test_scrub_collections_table success

Jim Witschey created CASSANDRA-10308:
----------------------------------------

             Summary: Investigate test_scrub_collections_table success
                 Key: CASSANDRA-10308
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10308
             Project: Cassandra
          Issue Type: Test
            Reporter: Jim Witschey
            Priority: Minor


As discussed [in dtest PR 431|https://github.com/riptano/cassandra-dtest/pull/431#issuecomment-126802307], {{scrub_test.py:TestScrubIndexes.test_scrub_collections_table}} started succeeding without any real explanation after [this commit to C*|https://github.com/apache/cassandra/commit/b70f7ea0ce27b5defa0a7773d448732364e7aee0]. I hate to be suspicious of a good thing, but I think it's worth investigating this to make sure that the test's success reflects reality and that no changes to Cassandra or the dtests had unintended consequences.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)