See https://builds.apache.org/job/Hadoop-Hdfs-trunk/3150/
###################################################################################
########################## LAST 60 LINES OF THE CONSOLE
###########################
[...truncated 5399 lines...]
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (create-testdirs) @ hadoop-hdfs-project
---
[INFO] Executing tasks
main:
[mkdir] Created dir:
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/target/test-dir
[INFO] Executed tasks
[INFO]
[INFO] --- maven-source-plugin:2.3:jar-no-fork (hadoop-java-sources) @
hadoop-hdfs-project ---
[INFO]
[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.5: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 [04:02 min]
[INFO] Apache Hadoop HDFS ................................ FAILURE [56:04 min]
[INFO] Apache Hadoop HDFS Native Client .................. SKIPPED
[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.140 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:00 h
[INFO] Finished at: 2016-05-16T22:20:49+00:00
[INFO] Final Memory: 57M/624M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on
project hadoop-hdfs: ExecutionException: java.lang.RuntimeException: The forked
VM terminated without properly saying goodbye. VM crash or System.exit called?
[ERROR] Command was /bin/sh -c cd
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/hadoop-hdfs
&& /home/jenkins/tools/java/jdk1.7.0_55/jre/bin/java -Xmx2048m
-XX:MaxPermSize=768m -XX:+HeapDumpOnOutOfMemoryError
-DminiClusterDedicatedDirs=true -jar
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefirebooter7514952471087814996.jar
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefire6774934879911219787tmp
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/hadoop-hdfs-project/hadoop-hdfs/target/surefire/surefire_214264296991204908227tmp
[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
Recording test results
Sending e-mails to: hdfs-dev@hadoop.apache.org
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
###################################################################################
############################## FAILED TESTS (if any)
##############################
2 tests failed.
FAILED:
org.apache.hadoop.hdfs.server.namenode.TestDiskspaceQuotaUpdate.testUpdateQuotaForFSync
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:46423,DS-0245426b-e66a-4029-b8b2-37633ce48435,DISK],
DatanodeInfoWithStorage[127.0.0.1:54837,DS-95931a37-e27e-4d6e-82d6-d96ea96e5cc9,DISK],
DatanodeInfoWithStorage[127.0.0.1:60175,DS-e590dfbe-21aa-4b54-8271-f41e9fae4628,DISK]],
original=[DatanodeInfoWithStorage[127.0.0.1:54837,DS-95931a37-e27e-4d6e-82d6-d96ea96e5cc9,DISK],
DatanodeInfoWithStorage[127.0.0.1:46423,DS-0245426b-e66a-4029-b8b2-37633ce48435,DISK],
DatanodeInfoWithStorage[127.0.0.1:60175,DS-e590dfbe-21aa-4b54-8271-f41e9fae4628,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:46423,DS-0245426b-e66a-4029-b8b2-37633ce48435,DISK],
DatanodeInfoWithStorage[127.0.0.1:54837,DS-95931a37-e27e-4d6e-82d6-d96ea96e5cc9,DISK],
DatanodeInfoWithStorage[127.0.0.1:60175,DS-e590dfbe-21aa-4b54-8271-f41e9fae4628,DISK]],
original=[DatanodeInfoWithStorage[127.0.0.1:54837,DS-95931a37-e27e-4d6e-82d6-d96ea96e5cc9,DISK],
DatanodeInfoWithStorage[127.0.0.1:46423,DS-0245426b-e66a-4029-b8b2-37633ce48435,DISK],
DatanodeInfoWithStorage[127.0.0.1:60175,DS-e590dfbe-21aa-4b54-8271-f41e9fae4628,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:1166)
at
org.apache.hadoop.hdfs.DataStreamer.addDatanode2ExistingPipeline(DataStreamer.java:1236)
at
org.apache.hadoop.hdfs.DataStreamer.handleDatanodeReplacement(DataStreamer.java:1427)
at
org.apache.hadoop.hdfs.DataStreamer.setupPipelineInternal(DataStreamer.java:1342)
at
org.apache.hadoop.hdfs.DataStreamer.setupPipelineForAppendOrRecovery(DataStreamer.java:1325)
at org.apache.hadoop.hdfs.DataStreamer.run(DataStreamer.java:603)
FAILED:
org.apache.hadoop.hdfs.server.namenode.TestDiskspaceQuotaUpdate.testUpdateQuotaForAppend
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:34766,DS-0bb838af-650e-4f18-974a-bf8ece688b7b,DISK],
DatanodeInfoWithStorage[127.0.0.1:55083,DS-baa4721d-45a7-4155-81a3-a7f53c8f1e55,DISK],
DatanodeInfoWithStorage[127.0.0.1:48185,DS-62cc5edd-a945-4ec4-817d-6ac79c3863ed,DISK]],
original=[DatanodeInfoWithStorage[127.0.0.1:34766,DS-0bb838af-650e-4f18-974a-bf8ece688b7b,DISK],
DatanodeInfoWithStorage[127.0.0.1:55083,DS-baa4721d-45a7-4155-81a3-a7f53c8f1e55,DISK],
DatanodeInfoWithStorage[127.0.0.1:48185,DS-62cc5edd-a945-4ec4-817d-6ac79c3863ed,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:34766,DS-0bb838af-650e-4f18-974a-bf8ece688b7b,DISK],
DatanodeInfoWithStorage[127.0.0.1:55083,DS-baa4721d-45a7-4155-81a3-a7f53c8f1e55,DISK],
DatanodeInfoWithStorage[127.0.0.1:48185,DS-62cc5edd-a945-4ec4-817d-6ac79c3863ed,DISK]],
original=[DatanodeInfoWithStorage[127.0.0.1:34766,DS-0bb838af-650e-4f18-974a-bf8ece688b7b,DISK],
DatanodeInfoWithStorage[127.0.0.1:55083,DS-baa4721d-45a7-4155-81a3-a7f53c8f1e55,DISK],
DatanodeInfoWithStorage[127.0.0.1:48185,DS-62cc5edd-a945-4ec4-817d-6ac79c3863ed,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:1166)
at
org.apache.hadoop.hdfs.DataStreamer.addDatanode2ExistingPipeline(DataStreamer.java:1236)
at
org.apache.hadoop.hdfs.DataStreamer.handleDatanodeReplacement(DataStreamer.java:1427)
at
org.apache.hadoop.hdfs.DataStreamer.setupPipelineInternal(DataStreamer.java:1342)
at
org.apache.hadoop.hdfs.DataStreamer.setupPipelineForAppendOrRecovery(DataStreamer.java:1325)
at org.apache.hadoop.hdfs.DataStreamer.run(DataStreamer.java:603)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
