Hadoop-Mapreduce-trunk - Build # 2806 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2806/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 33014 lines...] Tests run: 1, Failures: 0, Errors: 0

[jira] [Created] (MAPREDUCE-6601) Fix typo in Job#setUseNewAPI

Kai Sasaki created MAPREDUCE-6601: - Summary: Fix typo in Job#setUseNewAPI Key: MAPREDUCE-6601 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6601 Project: Hadoop Map/Reduce Issue Type:

Hadoop-Mapreduce-trunk - Build # 2805 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2805/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32913 lines...] Tests run: 1, Failures: 0, Errors: 0

Hadoop-Mapreduce-trunk-Java8 - Build # 867 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/867/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9692 lines...] +-org.apache.hadoop:hadoop-com

Hadoop-Mapreduce-trunk-Java8 - Build # 866 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/866/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9752 lines...] Running org.apache.hadoop.mapred

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

I agree that it would be a good practice to maintain parity between 2.6.x and 2.7.x as much as possible. Departure from it should be more of an exception than the norm. That said, it is also true that we're not exactly following the semantic versioning the moment we started to maintain multiple si

Hadoop-Mapreduce-trunk-Java8 - Build # 865 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/865/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10816 lines...] Running org.apache.hadoop.mapre

Hadoop-Mapreduce-trunk - Build # 2804 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2804/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32910 lines...] Running org.apache.hadoop.mapred.Tes

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

I like monotonic releases since it's simple for users to understand. Is it difficult to backport to 2.7.x if you're already backporting to 2.6.x? I don't follow why special casing some class of fixes is desirable. Also for maintenance releases, aren't all included fixes supposed to be for serious

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

The general rule sounds good to me. > "any fix in 2.x.y to be there in all 2.b.c releases (while b>=x) that get out after 2.x.y release date" +1 > I would prefer this rule only applies on critical/blocker fixes, but not applies on minor/trivial issues. +1 Thanks, Akira On 12/29/15 23:50,

Hadoop-Mapreduce-trunk-Java8 - Build # 864 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/864/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10819 lines...] Running org.apache.hadoop.mapre

Hadoop-Mapreduce-trunk - Build # 2803 - Still Failing

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2803/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 33377 lines...] TestAMWebServicesAttempts.:114->J