cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-6771) RangeTombstoneTest is failing on 2.1/trunk
Date Wed, 26 Feb 2014 00:06:19 GMT

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

Mime
View raw message