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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2829/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32932 lines...] Running org.apache.hadoop.mapreduce.

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/892/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10873 lines...] Java HotSpot(TM) 64-Bit Server

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2830/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32932 lines...] Tests run: 1, Failures: 0, Errors: 0

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/893/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9749 lines...] Running org.apache.hadoop.mapred

Re: [VOTE] Release Apache Hadoop 2.7.2 RC1

2016-01-14 Thread Junping Du
Thanks Vinod for working hard on this! It is really a huge effort to take care of a release with 154 commits. I did a sanity check for commits on 2.7.2, all looks fine except HDFS-8767 is missing from CHANGES.txt due to original commit issue. I already update it, and I think we are in good shap

[jira] [Resolved] (MAPREDUCE-6606) Findbug issue in org.apache.hadoop.mapred.OutputCommitter

2016-01-14 Thread Akira AJISAKA (JIRA)
[ https://issues.apache.org/jira/browse/MAPREDUCE-6606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akira AJISAKA resolved MAPREDUCE-6606. -- Resolution: Duplicate This issue was reported by MAPREDUCE-6595. Closing. > Findbug

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/894/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10097 lines...] Running org.apache.hadoop.mapre

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2831/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32977 lines...] Tests run: 1, Failures: 0, Errors: 0

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/895/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10818 lines...] Running org.apache.hadoop.mapre

[jira] [Created] (MAPREDUCE-6607) .staging dir is not cleanup if mapreduce.task.files.preserve.failedtask or mapreduce.task.files.preserve.filepattern are set

2016-01-14 Thread Maysam Yabandeh (JIRA)
Maysam Yabandeh created MAPREDUCE-6607: -- Summary: .staging dir is not cleanup if mapreduce.task.files.preserve.failedtask or mapreduce.task.files.preserve.filepattern are set Key: MAPREDUCE-6607 URL: https:/

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2832/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 35709 lines...] Running org.apache.hadoop.mapreduce.

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/896/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 10818 lines...] Running org.apache.hadoop.mapre

[UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Vinod Kumar Vavilapalli
Hi all, As some of you have noticed, we have an update from ASF infra on git branching policy: We no longer have a ASF wide mandate on disallowing force-pushes on all branches / tags. Summarizing information from the INFRA email for the sake of clarity in the midst of recent confusion - We no

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Vinod Kumar Vavilapalli
Mailing infra ate all the formatting up. Here’s the same email with some line breaks. > Hi all, > > As some of you have noticed, we have an update from ASF infra on git > branching policy: We no longer have a ASF wide mandate on disallowing > force-pushes on all branches / tags. > Summarizi

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2833/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31678 lines...] Tests run: 3, Failures: 0, Errors: 0

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/897/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9536 lines...] Running org.apache.hadoop.mapred

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Akira AJISAKA
Thanks Vinod for the information. +1 for removing origin/bracnh-2.8 and origin/sjlee/hdfs-merge. In addition, I'm thinking we need to delete origin/master, which was pushed wrongly. I've already deleted origin/ajisakaa/common-merge before force-push protection starts. > — There is a general rec

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/898/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9559 lines...] Running org.apache.hadoop.mapred

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2834/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 32858 lines...] Results : Tests in error: TestJ

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Yongjun Zhang
Thanks Vinod and Akira.. I assume we will have at least a committer review of any force-push. Say, if the commit history already has x, y, z, now we need to force push with x', we'd better not torget y and z, and if there is conflict putting in y and z after x', the conflict is better reviewed. M

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/899/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 8842 lines...] Java HotSpot(TM) 64-Bit Server V

[VOTE] Release Apache Hadoop 2.7.2 RC2

2016-01-14 Thread Vinod Kumar Vavilapalli
Hi all, I've created an updated release candidate RC2 for Apache Hadoop 2.7.2. As discussed before, this is the next maintenance release to follow up 2.7.1. The RC is available for validation at: http://people.apache.org/~vinodkv/hadoop-2.7.2-RC2/ The RC tag in git is: release-2.7.2-RC2 The m

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Vinod Kumar Vavilapalli
It kind of got lost through my email, but when I talked about force-push, it is almost completely in the context of feature-branch rebase. We almost never do force-push outside of this context, neither do we encourage it. And like I pointed, the fact that the mainline branches (trunk, branch-2

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Yongjun Zhang
Thanks for clarifying Vinod.That sounds good to me. --Yongjun On Thu, Jan 14, 2016 at 9:04 PM, Vinod Kumar Vavilapalli wrote: > It kind of got lost through my email, but when I talked about force-push, > it is almost completely in the context of feature-branch rebase. > > We almost never do for

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

2016-01-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2835/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 31678 lines...] Tests run: 3, Failures: 0, Errors: 0

Re: [UPDATE] New ASF git policy on force-pushes / Tags / Stale branches

2016-01-14 Thread Sangjin Lee
Thanks Vinod for the proposal. I deleted my branch (sjlee/hdfs-merge) the other day. Sangjin On Thu, Jan 14, 2016 at 1:26 PM, Vinod Kumar Vavilapalli wrote: > Hi all, > > As some of you have noticed, we have an update from ASF infra on git > branching policy: We no longer have a ASF wide mandat