You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuki Morishita (JIRA)" <ji...@apache.org> on 2014/02/26 01:06:19 UTC

[jira] [Resolved] (CASSANDRA-6771) RangeTombstoneTest is failing on 2.1/trunk

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

Yuki Morishita resolved CASSANDRA-6771.
---------------------------------------

    Resolution: Fixed

You are right. Test needed to be updated after CASSANDRA-6640.
Committed test fix in d0c38591bbf340ad4e998b66201b8e41a36dba8a.

> RangeTombstoneTest is failing on 2.1/trunk
> ------------------------------------------
>
>                 Key: CASSANDRA-6771
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6771
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Yuki Morishita
>            Priority: Minor
>             Fix For: 2.1 beta2
>
>
> RangeTombstoneTest#testOverwritesToDeletedColumns is failing with the following error:
> {code}
> [junit] Testcase: testOverwritesToDeletedColumns(org.apache.cassandra.db.RangeTombstoneTest):       FAILED
> [junit] expected:<2> but was:<1>
> [junit] junit.framework.AssertionFailedError: expected:<2> but was:<1>
> [junit]     at org.apache.cassandra.db.RangeTombstoneTest.testOverwritesToDeletedColumns(RangeTombstoneTest.java:345)
> {code}
> The test is checking if there is two index inserts happened, but this behavior seems to be changed since AtomicBTreeColumns, and now the test is producing one index insert and one index update.
> I'm not sure this is expected behavior and the test should be modified.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)