[
https://issues.apache.org/jira/browse/CASSANDRA-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709475#comment-14709475
]
Aleksey Yeschenko commented on CASSANDRA-10160:
-----------------------------------------------
Oh. Ok, makes sense.
So if we go with CASSANDRA-10146, then we should just stop running that test
for C* 3.0, since it's invalid.
> Test regression for write_failures_test.TestWriteFailures.test_mutation_v2
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-10160
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10160
> Project: Cassandra
> Issue Type: Bug
> Reporter: Sylvain Lebresne
> Assignee: Aleksey Yeschenko
> Fix For: 3.0 beta 2
>
>
> The dtest {{write_failures_test.TestWriteFailures.test_mutation_v2}} as
> started failing recently as shown by [its
> history|http://cassci.datastax.com/job/cassandra-3.0_dtest/lastBuild/testReport/write_failures_test/TestWriteFailures/test_mutation_v2/history/].
> From this history, the regression seems to be due to either CASSANDRA-6717
> (commit db782362aaf25214a94c393b20cdbade829c5291 to be exact) or
> CASSANDRA-6230 (CASSANDRA-10115 is also listed as change in the built that
> start to fail, but that ticket only modify a unit test so it's safe to assume
> it's not the cause).
> Assigning [~iamaleksey] since you've been involved in both of the tickets
> above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
