You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Joel Knighton (JIRA)" <ji...@apache.org> on 2015/12/14 23:09:46 UTC

[jira] [Commented] (CASSANDRA-10865) commitlog_test.py:TestCommitLog.test_bad_crc fails on C* 2.1

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

Joel Knighton commented on CASSANDRA-10865:
-------------------------------------------

This test was added as part of [CASSANDRA-9749], which only went in to 2.2 and above.

It seems we shouldn't be running this on 2.1.

> commitlog_test.py:TestCommitLog.test_bad_crc fails on C* 2.1
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-10865
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10865
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jim Witschey
>             Fix For: 2.1.x
>
>
> This test is failing hard on 2.1:
> http://cassci.datastax.com/job/cassandra-2.1_dtest/376/testReport/commitlog_test/TestCommitLog/test_bad_crc/history/
> In spite of having a bad commitlog, the node successfully starts. Is this a C* bug, or just something that wasn't implemented in 2.1? It seems to succeed on 2.2+.



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