Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 25 Oct 2016 05:34:58 +0000 (UTC)
From: "Stefania (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13013089.1476774412000.74882.1477373698757@Atlassian.JIRA>
In-Reply-To: <JIRA.13013089.1476774412000@Atlassian.JIRA>
References: <JIRA.13013089.1476774412000@Atlassian.JIRA> <JIRA.13013089.1476774412149@arcas>
Subject: [jira] [Commented] (CASSANDRA-12802) RecoveryManagerTruncateTest
 fails in 2.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 25 Oct 2016 05:35:02 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-12802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15604267#comment-15604267 ] 

Stefania commented on CASSANDRA-12802:
--------------------------------------

Noted, and if this is too risky then I suggest ignoring this test in 2.1. However, it is not just a test scenario, CASSANDRA-11743 could happen in 2.1 as well. The fix has been released in 2.2.7 and so far it has not caused problems that I know of, but let's hear [~blambov]'s opinion since I am still not that familiar with CL internals.

> RecoveryManagerTruncateTest fails in 2.1
> ----------------------------------------
>
>                 Key: CASSANDRA-12802
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12802
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Stefania
>            Assignee: Stefania
>             Fix For: 2.1.x
>
>
> Example failure:
> http://cassci.datastax.com/view/cassandra-2.1/job/cassandra-2.1_testall/388/testReport/junit/org.apache.cassandra.db/RecoveryManagerTruncateTest/testTruncatePointInTime/


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