[
https://issues.apache.org/jira/browse/CASSANDRA-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174435#comment-14174435
]
Michael Shuler commented on CASSANDRA-7713:
-------------------------------------------
I'm half-way thinking that the way to handle this timeout problem is to simply
add a test that is run immediately after CommitLogTest that simply resets
{{commitDir.setWritable(true);}}
> CommitLogTest failure causes cascading unit test failures
> ---------------------------------------------------------
>
> Key: CASSANDRA-7713
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7713
> Project: Cassandra
> Issue Type: Test
> Reporter: Michael Shuler
> Assignee: Bogdan Kanivets
> Fix For: 2.0.11
>
> Attachments: CommitLogTest.system.log.txt
>
>
> When CommitLogTest.testCommitFailurePolicy_stop fails or times out,
> {{commitDir.setWritable(true)}} is never reached, so the
> build/test/cassandra/commitlog directory is left without write permissions,
> causing cascading failure of all subsequent tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
