cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8570) org.apache.cassandra.db.compaction.CompactionsPurgeTest failing
Date Wed, 07 Jan 2015 12:55:35 GMT

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

Marcus Eriksson updated CASSANDRA-8570:
---------------------------------------
    Attachment: 0001-use-the-correct-repairedAt-value.patch

we pass in -1 to indicate that the repairedAt value used when creating the writer should be
used

> org.apache.cassandra.db.compaction.CompactionsPurgeTest failing
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-8570
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8570
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Philip Thompson
>            Assignee: Marcus Eriksson
>             Fix For: 2.1.3
>
>         Attachments: 0001-use-the-correct-repairedAt-value.patch
>
>
> The patch for CASSANDRA-8429 broke the tests {{org.apache.cassandra.db.compaction.CompactionsPurgeTest.testCompactionPurgeTombstonedRow}}
and {{org.apache.cassandra.db.compaction.CompactionsPurgeTest.testRowTombstoneObservedBeforePurging}}
> {code}
> junit.framework.AssertionFailedError: 
> 	at org.apache.cassandra.db.compaction.CompactionsPurgeTest.testCompactionPurgeTombstonedRow(CompactionsPurgeTest.java:308)
> {code}
> {code}expected:<0> but was:<1>
>  Stack Trace
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> 	at org.apache.cassandra.db.compaction.CompactionsPurgeTest.testRowTombstoneObservedBeforePurging(CompactionsPurgeTest.java:372)
> {code}



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

Mime
View raw message