Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 21 Jan 2016 17:14:39 +0000 (UTC)
From: "Philip Thompson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12924045.1450892661000.172647.1453396479877@Atlassian.JIRA>
In-Reply-To: <JIRA.12924045.1450892661000@Atlassian.JIRA>
References: <JIRA.12924045.1450892661000@Atlassian.JIRA>
 <JIRA.12924045.1450892661704@arcas>
Subject: [jira] [Resolved] (CASSANDRA-10933) index_summary_upgrade_test.py
 failing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Philip Thompson resolved CASSANDRA-10933.
-----------------------------------------
       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 3.0.x)
                       (was: 3.x)

> index_summary_upgrade_test.py failing
> -------------------------------------
>
>                 Key: CASSANDRA-10933
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10933
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Philip Thompson
>              Labels: dtest
>         Attachments: node1.log
>
>
> index_summary_upgrade_test.py is failing on HEAD for cassandra-3.0. The test upgrades from 2.1.3 to 3.0, and checks the following behavior
> {code}
> # on startup, it should detect that the old-format sstable had its
> # index summary downsampled (forcing it to be rebuilt)
> node.watch_log_for("Detected erroneously downsampled index summary")
> {code}
> However, this is not happening. The node's log is attached. It is quite possible that the "fix" here is that we only want to test upgrading from 2.1.3 to 2.1.LATEST, but that's not for me to decide. I can easily implement that, if that happens to be the case.


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