See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1292/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE 
###########################
[...truncated 11671 lines...]
     [exec] ^                                    changes.html
     [exec] * [47/6]    [1/29]    0.12s  8.4Kb   hftp.html
     [exec] * [48/5]    [0/0]     0.053s 10.6Kb  hftp.pdf
     [exec] X [0]                                     images/hdfs-logo.jpg      
BROKEN: 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/docs-src/src/documentation/content/xdocs/images.hdfs-logo.jpg
 (No such file or directory)
     [exec] * [50/3]    [0/0]     0.0050s 285b    images/instruction_arrow.png
     [exec] ^                                    api/index.html
     [exec] ^                                    jdiff/changes.html
     [exec] ^                                    releasenotes.html
     [exec] ^                                    changes.html
     [exec] * [51/3]    [1/29]    0.293s 27.3Kb  hdfs_imageviewer.html
     [exec] * [52/2]    [0/0]     0.182s 31.0Kb  hdfs_imageviewer.pdf
     [exec] * [54/0]    [0/0]     0.013s 766b    images/favicon.ico
     [exec] Total time: 0 minutes 11 seconds,  Site size: 696,806 Site pages: 43
     [exec] Java Result: 1
     [exec] 
     [exec] BUILD FAILED
     [exec] /home/jenkins/tools/forrest/latest/main/targets/site.xml:224: Error 
building site.
     [exec]         
     [exec] There appears to be a problem with your site build.
     [exec] 
     [exec] Read the output above:
     [exec] * Cocoon will report the status of each document:
     [exec]     - in column 1: *=okay X=brokenLink ^=pageSkipped (see FAQ).
     [exec] * Even if only one link is broken, you will still get "failed".
     [exec] * Your site would still be generated, but some pages would be 
broken.
     [exec]   - See 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/docs-src/build/site/broken-links.xml
     [exec] 
     [exec] Total time: 14 seconds
     [exec] 
     [exec]   Copying broken links file to site root.
     [exec]       
     [exec] Copying 1 file to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Hdfs-trunk/trunk/hadoop-hdfs-project/hadoop-hdfs/target/docs-src/build/site
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop HDFS ................................ FAILURE 
[1:21:01.653s]
[INFO] Apache Hadoop HttpFS .............................. SKIPPED
[INFO] Apache Hadoop HDFS BookKeeper Journal ............. SKIPPED
[INFO] Apache Hadoop HDFS Project ........................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:21:02.424s
[INFO] Finished at: Mon Jan 21 12:54:57 UTC 2013
[INFO] Final Memory: 31M/219M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.6:run (site) on project 
hadoop-hdfs: An Ant BuildException has occured: exec returned: 1 -> [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
Build step 'Execute shell' marked build as failure
Archiving artifacts
Updating HADOOP-8924
Sending e-mails to: hdfs-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



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

Reply via email to