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

Kihwal Lee commented on MAPREDUCE-4387:
---------------------------------------

I tested this idea and it worked. With {{-Pclover}}, TestRM always fails. With 
the added check, it succeeds.

BEFORE
{noformat}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.hadoop.yarn.server.resourcemanager.TestRM

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] hadoop-yarn-server-resourcemanager ................ FAILURE [5.180s]

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12:test (default-test) on 
project hadoop-yarn-server-resourcemanager: ExecutionException; nested 
exception is java.util.concurrent.ExecutionException: 
org.apache.maven.surefire.booter.SurefireBooterForkException: Error occurred in 
starting fork, check output in log -> [Help 1]
{noformat}


AFTER
{noformat}
-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.apache.hadoop.yarn.server.resourcemanager.TestRM
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.973 sec

Results :

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
{noformat}
                
> RM gets fatal error and exits during TestRM
> -------------------------------------------
>
>                 Key: MAPREDUCE-4387
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4387
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.0-alpha
>            Reporter: Kihwal Lee
>             Fix For: 2.0.1-alpha, 3.0.0
>
>
> It doesn't happen on my desktop, but it happens frequently during the builds 
> with clover enabled. Surefire will report it as fork failure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to