[ https://issues.apache.org/jira/browse/CASSANDRA-11220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178511#comment-15178511 ]
Philip Thompson edited comment on CASSANDRA-11220 at 3/3/16 8:03 PM: --------------------------------------------------------------------- Why would both SSTables expect "Repaired at: 0", if we've run sstablerepairedset against node2? EDIT: I've just seen the failing assertion is for max(matchcount), which fits with what I would expect. Opening a PR to correct that. was (Author: philipthompson): Why would both SSTables expect "Repaired at: 0", if we've run sstablerepairedset against node2? > repair_tests.incremental_repair_test.TestIncRepair.sstable_repairedset_test > failing > ----------------------------------------------------------------------------------- > > Key: CASSANDRA-11220 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11220 > Project: Cassandra > Issue Type: Test > Reporter: Russ Hatch > Assignee: Philip Thompson > Labels: dtest > > recent occurence: > http://cassci.datastax.com/job/cassandra-2.1_dtest/427/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test/ > last 2 runs failed: > http://cassci.datastax.com/job/cassandra-2.1_dtest/427/testReport/repair_tests.incremental_repair_test/TestIncRepair/sstable_repairedset_test/history/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)