cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12353) CustomIndexTest can still fail due to async cleanup
Date Mon, 01 Aug 2016 17:02:20 GMT

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

Sam Tunnicliffe updated CASSANDRA-12353:
----------------------------------------
    Status: Patch Available  (was: Open)

I've pushed a 3.0 branch, but won't waste electricity running 3.x CI.

||branch||testall||
|[12353-3.0|https://github.com/beobal/cassandra/tree/12353-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12353-3.0-testall]|


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

Mime
View raw message