cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10308) Investigate test_scrub_collections_table success
Date Fri, 11 Sep 2015 19:38:47 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-10308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741435#comment-14741435
] 

Paulo Motta commented on CASSANDRA-10308:
-----------------------------------------

does reverting that commit make the test fail again?

> 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
>            Assignee: 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)

Mime
View raw message