hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15229) Canary Tools should not call System.Exit on error
Date Wed, 10 Feb 2016 17:55:18 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141308#comment-15141308

Andrew Purtell commented on HBASE-15229:

This needs to be rebased after HBASE-15219. Let me do that now and commit.

> Canary Tools should not call System.Exit on error
> -------------------------------------------------
>                 Key: HBASE-15229
>                 URL: https://issues.apache.org/jira/browse/HBASE-15229
>             Project: HBase
>          Issue Type: Bug
>          Components: canary
>    Affects Versions: 0.98.17
>            Reporter: Vishal Khandelwal
>            Assignee: Vishal Khandelwal
>            Priority: Critical
>         Attachments: HBASE-15229.v1.patch, HBASE-15229.v2.patch, HBASE-15229.v3.patch
> run method in canary tool calls system.Exit on failure. Due to this it can't be integrated
as an API as jvm will stop on failure. It should only return (exit code)  
> So any integration with unit test also fail with
> {code}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.14:test
(default-test) on project <>: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.14:test
failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit
called ?
> {code}

This message was sent by Atlassian JIRA

View raw message