Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 2 Aug 2016 08:26:20 +0000 (UTC)
From: "Sam Tunnicliffe (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12994025.1470070658000.196754.1470126380772@Atlassian.JIRA>
In-Reply-To: <JIRA.12994025.1470070658000@Atlassian.JIRA>
References: <JIRA.12994025.1470070658000@Atlassian.JIRA> <JIRA.12994025.1470070658628@arcas>
Subject: [jira] [Updated] (CASSANDRA-12353) CustomIndexTest can still fail
 due to async cleanup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 02 Aug 2016 08:26:22 -0000


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

Sam Tunnicliffe updated CASSANDRA-12353:
----------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Ready to Commit)

Thanks, committed (with the additional update) to 3.0 in {{c6cb31e5f841f19eaccf6995fa7bd643b1e9acc3}} & merged to 3.9 & trunk.

> CustomIndexTest can still fail due to async cleanup
> ---------------------------------------------------
>
>                 Key: CASSANDRA-12353
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12353
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>
> CASSANDRA-11453 didn't quite go far enough in ensuring that indexes in {{CustomIndexTest}} are uniquely named. A couple of duplicates were missed which has lead to at least one failure (on trunk):
>  http://cassci.datastax.com/job/trunk_utest/1613/testReport/org.apache.cassandra.index/CustomIndexTest/customIndexRejectsExpressionSyntax/


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