See https://builds.apache.org/job/Hadoop-Hdfs-trunk/2154/
################################################################################### ########################## LAST 60 LINES OF THE CONSOLE ########################### [...truncated 6829 lines...] [INFO] --- maven-source-plugin:2.3:test-jar-no-fork (hadoop-java-sources) @ hadoop-hdfs-project --- [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (dist-enforce) @ hadoop-hdfs-project --- [INFO] [INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ hadoop-hdfs-project --- [INFO] [INFO] --- maven-javadoc-plugin:2.8.1:jar (module-javadocs) @ hadoop-hdfs-project --- [INFO] Skipping javadoc generation [INFO] [INFO] --- maven-enforcer-plugin:1.3.1:enforce (depcheck) @ hadoop-hdfs-project --- [INFO] [INFO] --- maven-checkstyle-plugin:2.15:checkstyle (default-cli) @ hadoop-hdfs-project --- [INFO] [INFO] --- findbugs-maven-plugin:3.0.0:findbugs (default-cli) @ hadoop-hdfs-project --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Apache Hadoop HDFS Client ......................... SUCCESS [ 45.948 s] [INFO] Apache Hadoop HDFS ................................ FAILURE [ 02:40 h] [INFO] Apache Hadoop HttpFS .............................. SKIPPED [INFO] Apache Hadoop HDFS BookKeeper Journal ............. SKIPPED [INFO] Apache Hadoop HDFS-NFS ............................ SKIPPED [INFO] Apache Hadoop HDFS Project ........................ SUCCESS [ 0.054 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:41 h [INFO] Finished at: 2015-06-12T14:16:05+00:00 [INFO] Final Memory: 55M/694M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project hadoop-hdfs: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire-reports for the individual test results. [ERROR] -> [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/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :hadoop-hdfs Build step 'Execute shell' marked build as failure Archiving artifacts Sending artifact delta relative to Hadoop-Hdfs-trunk #2153 Archived 1 artifacts Archive block size is 32768 Received 0 blocks and 362707 bytes Compression is 0.0% Took 6.4 sec Recording test results Updating YARN-3794 Updating HDFS-8566 Updating HDFS-8573 Updating HDFS-8583 Sending e-mails to: hdfs-dev@hadoop.apache.org Email was triggered for: Failure Sending email for trigger: Failure ################################################################################### ############################## FAILED TESTS (if any) ############################## 1 tests failed. REGRESSION: org.apache.hadoop.hdfs.server.namenode.TestFileTruncate.testTruncateFailure Error Message: Failed to replace a bad datanode on the existing pipeline due to no more good datanodes being available to try. (Nodes: current=[DatanodeInfoWithStorage[127.0.0.1:49533,DS-b6278782-d006-4ad9-9b27-e5358984f3f5,DISK], DatanodeInfoWithStorage[127.0.0.1:35413,DS-663663a0-79b0-4303-a08e-03be179daab0,DISK]], original=[DatanodeInfoWithStorage[127.0.0.1:49533,DS-b6278782-d006-4ad9-9b27-e5358984f3f5,DISK], DatanodeInfoWithStorage[127.0.0.1:35413,DS-663663a0-79b0-4303-a08e-03be179daab0,DISK]]). The current failed datanode replacement policy is DEFAULT, and a client may configure this via 'dfs.client.block.write.replace-datanode-on-failure.policy' in its configuration. Stack Trace: java.io.IOException: Failed to replace a bad datanode on the existing pipeline due to no more good datanodes being available to try. (Nodes: current=[DatanodeInfoWithStorage[127.0.0.1:49533,DS-b6278782-d006-4ad9-9b27-e5358984f3f5,DISK], DatanodeInfoWithStorage[127.0.0.1:35413,DS-663663a0-79b0-4303-a08e-03be179daab0,DISK]], original=[DatanodeInfoWithStorage[127.0.0.1:49533,DS-b6278782-d006-4ad9-9b27-e5358984f3f5,DISK], DatanodeInfoWithStorage[127.0.0.1:35413,DS-663663a0-79b0-4303-a08e-03be179daab0,DISK]]). The current failed datanode replacement policy is DEFAULT, and a client may configure this via 'dfs.client.block.write.replace-datanode-on-failure.policy' in its configuration. at org.apache.hadoop.hdfs.DataStreamer.findNewDatanode(DataStreamer.java:1145) at org.apache.hadoop.hdfs.DataStreamer.addDatanode2ExistingPipeline(DataStreamer.java:1211) at org.apache.hadoop.hdfs.DataStreamer.handleDatanodeReplacement(DataStreamer.java:1375) at org.apache.hadoop.hdfs.DataStreamer.setupPipelineForAppendOrRecovery(DataStreamer.java:1289) at org.apache.hadoop.hdfs.DataStreamer.run(DataStreamer.java:586)
