Hadoop-Mapreduce-trunk - Build # 1387 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1387/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 29060 lines...]
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.659 sec
Running org.apache.hadoop.mapreduce.lib.partition.TestTotalOrderPartitioner
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.878 sec
Running org.apache.hadoop.mapreduce.lib.partition.TestMRKeyFieldBasedComparator
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.963 sec
Running org.apache.hadoop.mapreduce.lib.partition.TestKeyFieldHelper
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.136 sec
Running org.apache.hadoop.mapreduce.lib.partition.TestBinaryPartitioner
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.44 sec
Running org.apache.hadoop.mapreduce.lib.partition.TestMRKeyFieldBasedPartitioner
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.402 sec
Running org.apache.hadoop.mapreduce.TestChild
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.603 sec
Running org.apache.hadoop.mapreduce.filecache.TestURIFragments
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.06 sec
Running org.apache.hadoop.mapreduce.TestMapReduce
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.696 sec

Results :

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

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-mapreduce-client ... SUCCESS [1.625s]
[INFO] hadoop-mapreduce-client-core .. SUCCESS [28.593s]
[INFO] hadoop-mapreduce-client-common  SUCCESS [23.956s]
[INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [2.020s]
[INFO] hadoop-mapreduce-client-app ... SUCCESS [5:07.661s]
[INFO] hadoop-mapreduce-client-hs  SUCCESS [1:11.893s]
[INFO] hadoop-mapreduce-client-jobclient . FAILURE [41:56.791s]
[INFO] hadoop-mapreduce-client-hs-plugins  SKIPPED
[INFO] Apache Hadoop MapReduce Examples .. SKIPPED
[INFO] hadoop-mapreduce .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 49:13.174s
[INFO] Finished at: Sat Mar 30 14:03:49 UTC 2013
[INFO] Final Memory: 20M/142M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on 
project hadoop-mapreduce-client-jobclient: 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 ? - [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn goals -rf :hadoop-mapreduce-client-jobclient
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Updating YARN-515
Updating YARN-460
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (MAPREDUCE-5120) Allow app master to use tracing async dispatcher

[Sandy Ryza (JIRA)]

Sandy Ryza created MAPREDUCE-5120:
-

 Summary: Allow app master to use tracing async dispatcher
 Key: MAPREDUCE-5120
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5120
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: applicationmaster
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza


YARN-366 proposes an option to add traces to events so that exceptions could 
report an events lineage.  This JIRA would add a mapreduce config option that 
would allow the MR app master to use the tracing async dispatcher as well. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira