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

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE 
###########################
[...truncated 28674 lines...]
Results :

Failed tests:   testCrashed(org.apache.hadoop.mapreduce.v2.app.TestRecovery): 
Task state is not correct (timedout) expected:<SUCCEEDED> but was:<RUNNING>
  testMultipleCrashes(org.apache.hadoop.mapreduce.v2.app.TestRecovery): Task 
state is not correct (timedout) expected:<SUCCEEDED> but was:<RUNNING>
  testOutputRecovery(org.apache.hadoop.mapreduce.v2.app.TestRecovery): Task 
state is not correct (timedout) expected:<SUCCEEDED> but was:<RUNNING>
  testOutputRecoveryMapsOnly(org.apache.hadoop.mapreduce.v2.app.TestRecovery): 
Task state is not correct (timedout) expected:<SUCCEEDED> but was:<RUNNING>
  testUpdatedNodes(org.apache.hadoop.mapreduce.v2.app.TestMRApp): Task state is 
not correct (timedout) expected:<SUCCEEDED> but was:<RUNNING>

Tests in error: 
  
testAMInfosWithoutRecoveryEnabled(org.apache.hadoop.mapreduce.v2.app.TestAMInfos):
 org.codehaus.jackson.JsonParseException: Unexpected end-of-input: was 
expecting closing '"' for name(..)
  
testFirstFlushOnCompletionEvent(org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler):
 (..)
  
testMaxUnflushedCompletionEvents(org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler):
 (..)
  
testUnflushedTimer(org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler):
 (..)
  
testBatchedFlushJobEndMultiplier(org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler):
 (..)

Tests run: 180, Failures: 4, Errors: 5, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-mapreduce-client ........................... SUCCESS [2.119s]
[INFO] hadoop-mapreduce-client-core ...................... SUCCESS [17.805s]
[INFO] hadoop-mapreduce-client-common .................... SUCCESS [21.808s]
[INFO] hadoop-mapreduce-client-shuffle ................... SUCCESS [1.069s]
[INFO] hadoop-mapreduce-client-app ....................... FAILURE [5:06.642s]
[INFO] hadoop-mapreduce-client-hs ........................ SKIPPED
[INFO] hadoop-mapreduce-client-jobclient ................. SKIPPED
[INFO] Apache Hadoop MapReduce Examples .................. SKIPPED
[INFO] hadoop-mapreduce .................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5:49.991s
[INFO] Finished at: Thu Nov 15 13:21:09 UTC 2012
[INFO] Final Memory: 22M/253M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.3: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 ? 
-> [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-app
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Updating HADOOP-9042
Updating HDFS-4182
Updating MAPREDUCE-4797
Updating MAPREDUCE-4720
Updating HDFS-4171
Updating MAPREDUCE-4723
Updating HADOOP-9037
Updating YARN-216
Email was triggered for: Failure
Sending email for trigger: Failure



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

Reply via email to