cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-282) system tests fail straingely if an instance is running
Date Fri, 10 Jul 2009 12:37:14 GMT

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

Hudson commented on CASSANDRA-282:
----------------------------------

Integrated in Cassandra #133 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/133/])
    abort system tests if previous run shutdown uncleanly

Patch by eevans; reviewed by Michael Greene for 
move ports used in system tests; shorten timeout

Patch by Michael Greene; reviewed by eevans for 


> system tests fail straingely if an instance is running
> ------------------------------------------------------
>
>                 Key: CASSANDRA-282
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-282
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Eric Evans
>            Assignee: Michael Greene
>         Attachments: 0001-CASSANDRA-282-stop-drop-roll-if-uncleanly-shutdown.txt, 282-v1.diff
>
>
> The system tests blow up spectacularly if there is another instance of cassandra running
(and it can be difficult to tell that this is why). Having the harness start its instance
using alternate ports would prevent this from happening in some cases, but something should
be done to test for instances left over from failed tests, and at least produce clearer error
messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message