[
https://issues.apache.org/jira/browse/CASSANDRA-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700858#comment-14700858
]
Benedict commented on CASSANDRA-10094:
--------------------------------------
I'm not sure what went wrong, to be honest. I committed the 2.2 patch and
merged upwards, but I was notified 3.0 and trunk were still failing, so figured
I'd messed up by not taking the pre-merged 3.0 when merging upwards beyond 2.2,
so applied this only as a correction. I guess I had really applied the prior
version of the patch. I'll apply the backport shortly.
> 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
>
> Attachments: 10094-2.2.txt
>
>
> 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)
