cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bogdan Kanivets (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7713) CommitLogTest failure causes cascading unit test failures
Date Fri, 17 Oct 2014 01:09:34 GMT

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

Bogdan Kanivets commented on CASSANDRA-7713:
--------------------------------------------

Another way is to not use sleepUninterruptibly. It looks like this prevents 'finally' block
to execute in time. That was my original solution, but then I've noticed that there is more
general problem with the test - when you remove 'logFile.setWritable(false)' it still passes.

I'll try to look into it this weekend to get a patch (have been busy lately), but feel free
to reassign

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

Mime
View raw message