You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/03/17 11:30:33 UTC
[jira] [Commented] (CASSANDRA-10340) Stress should exit with
non-zero status after failure
[ https://issues.apache.org/jira/browse/CASSANDRA-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199276#comment-15199276 ]
Stefania commented on CASSANDRA-10340:
--------------------------------------
Patch and tests for trunk:
|[patch|https://github.com/stef1927/cassandra/commits/10340]|[testall|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-10340-testall/]|[dtest|http://cassci.datastax.com/view/Dev/view/stef1927/job/stef1927-10340-dtest/]|
The patch attached should meet the requirements. There are still several calls to {{System.exit(1)}}, it would be nice to remove them all at some point.
> Stress should exit with non-zero status after failure
> -----------------------------------------------------
>
> Key: CASSANDRA-10340
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10340
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Paulo Motta
> Assignee: Stefania
> Priority: Minor
> Labels: lhf, stress
> Fix For: 3.x
>
>
> Currently, stress always exits with sucess status, even if after a failure. In order to be able to rely on stress exit status during dtests it would be nice if it exited with a non-zero status after failures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)