See https://builds.apache.org/job/Hadoop-Yarn-trunk/280/
################################################################################### ########################## LAST 60 LINES OF THE CONSOLE ########################### [...truncated 12741 lines...] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.885 sec Running org.apache.hadoop.yarn.server.nodemanager.webapp.TestNMWebServicesContainers Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.492 sec Results : Tests in error: testLocalFilesCleanup(org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager): java.util.zip.ZipException: oversubscribed dynamic bit lengths tree testContainerLaunchFromPreviousRM(org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager): java.util.zip.ZipException: oversubscribed dynamic bit lengths tree testMultipleContainersLaunch(org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager): java.util.zip.ZipException: oversubscribed dynamic bit lengths tree testMultipleContainersStopAndGetStatus(org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager): java.util.zip.ZipException: oversubscribed dynamic bit lengths tree Tests run: 185, Failures: 0, Errors: 4, Skipped: 1 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] hadoop-yarn ....................................... SUCCESS [6.370s] [INFO] hadoop-yarn-api ................................... SUCCESS [1:55.286s] [INFO] hadoop-yarn-common ................................ SUCCESS [2:05.064s] [INFO] hadoop-yarn-server ................................ SUCCESS [0.110s] [INFO] hadoop-yarn-server-common ......................... SUCCESS [27.491s] [INFO] hadoop-yarn-server-nodemanager .................... FAILURE [3:07.854s] [INFO] hadoop-yarn-server-web-proxy ...................... SKIPPED [INFO] hadoop-yarn-server-resourcemanager ................ SKIPPED [INFO] hadoop-yarn-server-tests .......................... SKIPPED [INFO] hadoop-yarn-client ................................ SKIPPED [INFO] hadoop-yarn-applications .......................... SKIPPED [INFO] hadoop-yarn-applications-distributedshell ......... SKIPPED [INFO] hadoop-yarn-applications-unmanaged-am-launcher .... SKIPPED [INFO] hadoop-yarn-site .................................. SKIPPED [INFO] hadoop-yarn-project ............................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7:43.450s [INFO] Finished at: Wed Jul 24 10:41:18 UTC 2013 [INFO] Final Memory: 45M/777M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on project hadoop-yarn-server-nodemanager: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/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-yarn-server-nodemanager Build step 'Execute shell' marked build as failure Archiving artifacts Error updating JIRA issues. Saving issues for next build. com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Attempt to log in user 'hudson' 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. Sending e-mails to: [email protected] Email was triggered for: Failure Sending email for trigger: Failure ################################################################################### ############################## FAILED TESTS (if any) ############################## No tests ran.
