[ 
https://issues.apache.org/jira/browse/CASSANDRA-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174391#comment-14174391
 ] 

Michael Shuler commented on CASSANDRA-7713:
-------------------------------------------

An @AfterClass didn't help, either..
{noformat}
diff --git a/test/unit/org/apache/cassandra/db/CommitLogTest.java 
b/test/unit/org/apache/cassandra/db/CommitLogTest.java
index 1be29a6..19faace 100644
--- a/test/unit/org/apache/cassandra/db/CommitLogTest.java
+++ b/test/unit/org/apache/cassandra/db/CommitLogTest.java
@@ -29,6 +29,7 @@ import java.util.zip.Checksum;
 
 import com.google.common.util.concurrent.Uninterruptibles;
 import org.junit.Assert;
+import org.junit.AfterClass;
 import org.junit.Test;
 
 import org.apache.cassandra.SchemaLoader;
@@ -48,6 +49,15 @@ import static 
org.apache.cassandra.utils.ByteBufferUtil.bytes;
 
 public class CommitLogTest extends SchemaLoader
 {
+    @AfterClass
+    public static void resetCommitLogDir()
+    {
+        // junit timeout leaves commitDir non-writable - CASSANDRA-7713
+        File commitDir = new File(DatabaseDescriptor.getCommitLogLocation());
+        commitDir.setWritable(true);
+        System.out.println("reset commitlogdir: " + commitDir);
+    }
+
     @Test
     public void testRecoveryWithEmptyLog() throws Exception
     {
{noformat}

> 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)

Reply via email to