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/07/09 21:42:04 UTC

[jira] [Created] (CASSANDRA-9774) sstableverify doesn't detect missing sstables on trunk

Jim Witschey created CASSANDRA-9774:
---------------------------------------

             Summary: sstableverify doesn't detect missing sstables on trunk
                 Key: CASSANDRA-9774
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9774
             Project: Cassandra
          Issue Type: Sub-task
            Reporter: Jim Witschey
            Priority: Blocker
             Fix For: 3.0.x


One of our dtests for {{sstableverify}} ({{offline_tools_test.py:TestOfflineTools.sstableverify_test}}) is failing hard on trunk ([cassci history|http://cassci.datastax.com/view/trunk/job/trunk_dtest/lastCompletedBuild/testReport/offline_tools_test/TestOfflineTools/sstableverify_test/history/])

The way the test works is by deleting an SSTable, then running {{sstableverify}} on its table. In earlier versions, it successfully detects this problem and outputs that it "was not released before the reference was garbage collected". The test no longer finds this string in the output; looking through the output of the test, it doesn't look like it reports any problems at all.



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