cassandra-commits mailing list archives

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

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

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

Without any recommendation on CASSANDRA-7927, since I haven't had a good look at it, we don't
want to close this ticket without fixing/replacing/removing/something CommitFailurePolicy_stop
leaving this non-writable dir behind - not only do following tests fail, things like `git
clean -df` don't work, if this test dorks.  :)

I'd be happy if the solution was to pass in a code trigger of some sort than actually setting
the dir read-only - whatever tests functionality properly.

> 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