Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 9 Jan 2014 21:07:51 +0000 (UTC)
From: "Jinghui Wang (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12687955.1389219884621.71413.1389301671469@arcas>
In-Reply-To: <JIRA.12687955.1389219884621@arcas>
References: <JIRA.12687955.1389219884621@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5714) TestMRAppComponentDependencies
 causes surefire to exit without saying proper goodbye
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jinghui Wang commented on MAPREDUCE-5714:
-----------------------------------------

Added patch to remove the System.exit() call.

> TestMRAppComponentDependencies causes surefire to exit without saying proper goodbye
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5714
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5714
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 2.2.0
>         Environment: RHEL 6.4 
>            Reporter: Jinghui Wang
>             Fix For: 2.2.0
>
>         Attachments: MAPREDUCE-5714.patch
>
>
> When running test TestMRAppComponentDependencies, surefire exits with the following message: 
> Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project hadoop-mapreduce-client-app: ExecutionException; nested exception is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ?
> The following code is found in o.a.h.mapreduce.v2.app.MRAppMaster#shutDownJob, which the test case inherits. So, before the test testComponentStopOrder completes in TestMRAppComponentDependencies, shutDownJob finishes executing and exits the JVM, thus causing the error. Based on the comment, the System.exit(0) is there as a workaround for before HADOOP-7140. Since the patch for HADOOP-7140 is committed in branch-2, are we safe to remove the System.exit call now.
>     //Bring the process down by force.
>     //Not needed after HADOOP-7140
>     LOG.info("Exiting MR AppMaster..GoodBye!");
>     sysexit();
>  


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)