Hadoop-Mapreduce-trunk-Java8 - Build # 282 - Still Failing
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/282/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10689 lines...] Results : Failed tests: TestJobEndNotifier.checkConfiguration:150-testProxyConfiguration:124 Proxy should have been set but wasn't TestJobEndNotifier.testNotifyRetries:180 Should have taken more than 5 seconds it took 149 Tests run: 331, Failures: 2, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache Hadoop MapReduce Client SUCCESS [ 2.665 s] [INFO] Apache Hadoop MapReduce Core .. SUCCESS [01:18 min] [INFO] Apache Hadoop MapReduce Common SUCCESS [ 25.873 s] [INFO] Apache Hadoop MapReduce Shuffle ... SUCCESS [ 4.069 s] [INFO] Apache Hadoop MapReduce App ... FAILURE [10:01 min] [INFO] Apache Hadoop MapReduce HistoryServer . SKIPPED [INFO] Apache Hadoop MapReduce JobClient . SKIPPED [INFO] Apache Hadoop MapReduce HistoryServer Plugins . SKIPPED [INFO] Apache Hadoop MapReduce NativeTask SKIPPED [INFO] Apache Hadoop MapReduce Examples .. SKIPPED [INFO] Apache Hadoop MapReduce ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 11:53 min [INFO] Finished at: 2015-08-12T14:27:26+00:00 [INFO] Final Memory: 40M/256M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on project hadoop-mapreduce-client-app: There are test failures. [ERROR] [ERROR] Please refer to /home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-trunk-Java8/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/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-mapreduce-client-app Build step 'Execute shell' marked build as failure [FINDBUGS] Skipping publisher since build result is FAILURE Archiving artifacts Sending artifact delta relative to Hadoop-Mapreduce-trunk-Java8 #276 Archived 1 artifacts Archive block size is 32768 Received 0 blocks and 20459142 bytes Compression is 0.0% Took 11 sec Recording test results Updating HDFS-8805 Updating YARN-4023 Updating HDFS-8887 Updating YARN-3999 Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## 2 tests failed. FAILED: org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier.checkConfiguration Error Message: Proxy should have been set but wasn't Stack Trace: java.lang.AssertionError: Proxy should have been set but wasn't at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier.testProxyConfiguration(TestJobEndNotifier.java:124) at org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier.checkConfiguration(TestJobEndNotifier.java:150) FAILED: org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier.testNotifyRetries Error Message: Should have taken more than 5 seconds it took 149 Stack Trace: java.lang.AssertionError: Should have taken more than 5 seconds it took 149 at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.apache.hadoop.mapreduce.v2.app.TestJobEndNotifier.testNotifyRetries(TestJobEndNotifier.java:180)
Re: Hadoop 2.6.1 Release process thread
I've just applied the 2.6.1-candidate label to HADOOP-10786. Since this is somewhat late in the process, I thought I'd better follow up over email too. This bug was originally reported with JDK 8. A code change in JDK 8 broke our automatic relogin from a Kerberos keytab, and we needed to change UserGroupInformation to fix it. Just today I discovered that the JDK code change has made it into the JDK 7 code line too. Specifically, I can repro the bug against OpenJDK 1.7.0_85. Since many users wouldn't expect a minor version upgrade of the JDK to cause such a severe problem, I think HADOOP-10786 is justified for inclusion in a patch release. --Chris Nauroth On 8/11/15, 7:48 PM, Sangjin Lee sjl...@gmail.com wrote: It might have been because we thought that HDFS-7704 was going to make it. It's both make it or neither does. Now that we know HDFS-7704 is out, HDFS-7916 should definitely be out. I hope that clarifies. On Tue, Aug 11, 2015 at 6:26 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: I earlier removed HDFS-7916 from the list given HDFS-7704 was only in 2.7.0. Chris Trezzo added it back and so it appeared in my lists. I removed it again, Chris, please comment on why you added it back. If you want it included, please comment here and we can add it after we figure out the why and the dependent tickets. Thanks +Vinod On Aug 11, 2015, at 4:37 PM, Sangjin Lee sjl...@gmail.commailto: sjl...@gmail.com wrote: Could you double check HDFS-7916? HDFS-7916 is needed only if HDFS-7704 makes it. However, I see commits for HDFS-7916 in this list, but not for HDFS-7704. If HDFS-7704 is not in the list, we should not backport HDFS-7916 as it fixes an issue introduced by HDFS-7704. On Tue, Aug 11, 2015 at 4:10 PM, Vinod Kumar Vavilapalli vino...@hortonworks.commailto:vino...@hortonworks.com wrote: Put the list here: https://wiki.apache.org/hadoop/Release-2.6.1-Working-Notes. And started figuring out ways to fast-path the cherry-picks. Thanks +Vinod On Aug 11, 2015, at 1:15 PM, Vinod Kumar Vavilapalli vino...@apache.org mailto:vino...@apache.org wrote: (2) With Wangda's help offline, I prepared an ordered list of cherry-pick commits that we can do from our candidate list [1], will do some ground work today.
Re: Planning Hadoop 2.6.1 release
Can we include YARN-3999 too, if the list is not yet frozen. On Aug 11, 2015, at 1:49 PM, Hitesh Shah hit...@apache.org wrote: Jason Lowe just filed YARN-4047 ( patch available too ) which probably is also a good candidate for 2.6.1 or 2.6.2 if the list is frozen. I have labelled the jira as a 2.6.1 candidate. Feel free to switch to 2.6.2 if needed. thanks — Hitesh On Aug 10, 2015, at 4:15 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: As of now, I am freezing the list. We have 139 tickets to go through, find the right order, get them committed etc. I’ll start a separate thread for this one-time long release-process of 2.6.1. Thanks everyone for pitching in. +Vinod On Aug 10, 2015, at 4:13 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Added them all, tx Rohit. +Vinod On Aug 5, 2015, at 9:51 PM, Rohith Sharma K S rohithsharm...@huawei.com wrote: Can we add following fixes to 2.6.1? YARN-3733 YARN-2865 YARN-3990 YARN-2894 Thanks Regards Rohith Sharma K S -Original Message- From: Allan Wilson [mailto:awils...@pandora.com] Sent: 05 August 2015 23:25 To: common-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org Cc: hdfs-...@hadoop.apache.org Subject: Re: Planning Hadoop 2.6.1 release Another +1 to add those fixes. YARN-3487 bug can grind a large cluster to a halt repeatedly -Allan Allan Wilson | Sr. Software Engineer | Pandora m 919.841.2449 | awils...@pandora.com On 8/5/15, 1:52 PM, Rich Haase rha...@pandora.com wrote: +1 to add those fixes. Rich Haase | Sr. Software Engineer | Pandora m 303.887.1146 | rha...@pandora.com On 8/5/15, 11:42 AM, Wangda Tan wheele...@gmail.com wrote: Can we add following two fixes to 2.6.1? https://issues.apache.org/jira/browse/YARN-2922 and https://issues.apache.org/jira/browse/YARN-3487. They're not fatal issue, but they can cause lots of issue in a large cluster. Thanks, Wangda On Mon, Aug 3, 2015 at 1:21 PM, Sangjin Lee sj...@apache.org wrote: See my later update in the thread. HDFS-7704 is in the list. Thanks, Sangjin On Mon, Aug 3, 2015 at 1:19 PM, Vinod Kumar Vavilapalli vino...@hortonworks.com wrote: Makes sense, it was caused by HDFS-7704 which got into 2.7.0 only and is not part of the candidate list. Removed HDFS-7916 from the list. Thanks +Vinod On Jul 24, 2015, at 6:32 PM, Sangjin Lee sj...@apache.org wrote: Out of the JIRAs we proposed, please remove HDFS-7916. I don't think it applies to 2.6. Thanks, Sangjin
