[
https://issues.apache.org/jira/browse/CASSANDRA-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700138#comment-14700138
]
Paulo Motta commented on CASSANDRA-10094:
-----------------------------------------
[~JoshuaMcKenzie] I originally created that patch for 2.2+ in the context of
[CASSANDRA-8515|https://issues.apache.org/jira/browse/CASSANDRA-8515]. However
there was a problem with the tests not executing correctly on cassci due to
other problems. In the mean time, I noticed one of the tests was still not
working on Windows and updated the original patch, but forgot to mention it on
the JIRA ticket (sorry for that). After tests were passing on cassci,
[~benedict] probably commited an older version of the patch. I suppose
d2da7606abebd98b11f8b7ec692aa7dcf5388151 was basically to update the original
commit to the updated patch, but it was only applied to 3.0+, it needs to be
backported to 2.2.
> Windows utest 2.2: testCommitLogFailureBeforeInitialization_mustKillJVM
> failure
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-10094
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10094
> Project: Cassandra
> Issue Type: Bug
> Reporter: Joshua McKenzie
> Assignee: Paulo Motta
> Labels: Windows
> Fix For: 2.2.x
>
>
> Error:
> {noformat}
> junit.framework.AssertionFailedError:
> at
> org.apache.cassandra.db.CommitLogFailurePolicyTest.testCommitLogFailureBeforeInitialization_mustKillJVM(CommitLogFailurePolicyTest.java:149)
> {noformat}
> [Failure
> History|http://cassci.datastax.com/view/cassandra-2.2/job/cassandra-2.2_utest_win32/lastCompletedBuild/testReport/org.apache.cassandra.db/CommitLogFailurePolicyTest/testCommitLogFailureBeforeInitialization_mustKillJVM/history/]:
> Consistent since build #85
> Env: CI only. Cannot repro locally
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
