Jira: https://issues.apache.org/jira/browse/YARN-3293 Build: https://builds.apache.org/job/PreCommit-YARN-Build/7254/
################################################################################### ########################## LAST 60 LINES OF THE CONSOLE ########################### [...truncated 37 lines...] Fast-forwarded trunk to dd852f5b8c8fe9e52d15987605f36b5b60f02701. YARN-3293 patch is being downloaded at Wed Apr 8 15:10:24 UTC 2015 from http://issues.apache.org/jira/secure/attachment/12723930/apache-yarn-3293.6.patch cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory ====================================================================== ====================================================================== Pre-build trunk to verify trunk stability and javac warnings ====================================================================== ====================================================================== Compiling /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build /home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests -DHadoopPatchProcess -Ptest-patch > /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/trunkJavacWarnings.txt 2>&1 /home/jenkins/tools/maven/latest/bin/mvn clean test javadoc:javadoc -DskipTests -Pdocs -DHadoopPatchProcess > /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/trunkJavadocWarnings.txt 2>&1 /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/dev-support/test-patch.sh: line 310: /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/trunkJavadocWarnings.txt: No such file or directory Trunk javadoc compilation is broken? {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12723930/apache-yarn-3293.6.patch against trunk revision dd852f5. {color:red}-1 patch{color}. Trunk compilation may be broken. Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7254//console This message is automatically generated. ====================================================================== ====================================================================== Adding comment to Jira. ====================================================================== ====================================================================== Unable to log in to server: https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: hadoopqa. Cause: com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Attempt to log in user 'hadoopqa' failed. The maximum number of failed login attempts has been reached. Please log into the application through the web interface to reset the number of failed login attempts. Unable to log in to server: https://issues.apache.org/jira/rpc/soap/jirasoapservice-v2 with user: hadoopqa. Cause: com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Attempt to log in user 'hadoopqa' failed. The maximum number of failed login attempts has been reached. Please log into the application through the web interface to reset the number of failed login attempts. ====================================================================== ====================================================================== Finished build. ====================================================================== ====================================================================== Build step 'Execute shell' marked build as failure Archiving artifacts [description-setter] Could not determine description. Recording test results Email was triggered for: Failure Sending email for trigger: Failure ################################################################################### ############################## FAILED TESTS (if any) ############################## No tests ran.
