Jira: https://issues.apache.org/jira/browse/TEZ-3244 Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2239/
################################################################################### ########################## LAST 60 LINES OF THE CONSOLE ########################### [...truncated 4717 lines...] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :tez-dag [INFO] Build failures were ignored. {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12851242/TEZ-3244.003.patch against master revision b3a3af3. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 3.0.1) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 core tests{color}. The patch failed these unit tests in : org.apache.tez.dag.app.rm.TestTaskSchedulerManager Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/2239//testReport/ Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2239//console This message is automatically generated. ====================================================================== ====================================================================== Adding comment to Jira. ====================================================================== ====================================================================== Comment added. 27b4c24717a6084c7a73eaed78b9a888cbf7c4ec logged out ====================================================================== ====================================================================== 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 - Any Sending email for trigger: Failure - Any ################################################################################### ############################## FAILED TESTS (if any) ############################## 1 tests failed. FAILED: org.apache.tez.dag.app.rm.TestTaskSchedulerManager.testReportFailureFromTaskScheduler Error Message: test timed out after 5000 milliseconds Stack Trace: java.lang.Exception: test timed out after 5000 milliseconds at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:901) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1295) at java.net.InetAddress.getAllByName0(InetAddress.java:1248) at java.net.InetAddress.getAllByName(InetAddress.java:1164) at java.net.InetAddress.getAllByName(InetAddress.java:1098) at java.net.InetAddress.getByName(InetAddress.java:1048) at java.net.InetSocketAddress.<init>(InetSocketAddress.java:220) at org.apache.tez.dag.app.rm.TestTaskSchedulerManager.testReportFailureFromTaskScheduler(TestTaskSchedulerManager.java:581)
