Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 23 Mar 2016 19:19:26 +0000 (UTC)
From: "Philip Thompson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12921808.1450133356000.33107.1458760766062@Atlassian.JIRA>
In-Reply-To: <JIRA.12921808.1450133356000@Atlassian.JIRA>
References: <JIRA.12921808.1450133356000@Atlassian.JIRA>
 <JIRA.12921808.1450133356951@arcas>
Subject: [jira] [Resolved] (CASSANDRA-10868) Skip supercolumns upgrade tests
 on jdk8
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Philip Thompson resolved CASSANDRA-10868.
-----------------------------------------
    Resolution: Fixed

Jim's PR fixed this ages ago. New failures reasons are being tracked in CASSANDRA-11078

> Skip supercolumns upgrade tests on jdk8
> ---------------------------------------
>
>                 Key: CASSANDRA-10868
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10868
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>            Assignee: Jim Witschey
>
> The tests in the {{upgrade_supercolumns_test}} dtest module fail when we test on JDK8 because they attempt to upgrade from 2.0, which will not compile on JDK8:
> http://cassci.datastax.com/job/cassandra-2.1_dtest_jdk8/160/testReport/upgrade_supercolumns_test/
> [~rhatch] As we look at how we want to run upgrade tests in the future, we should consider this. In the meantime, I think the best way to deal with this might be to add something to the exclude files in {{conf/}}. That sound reasonable, or is there a better way to do this?


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