Failed: YARN-3264 PreCommit Build #6835

Jira: https://issues.apache.org/jira/browse/YARN-3264 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6835/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Hadoop-Yarn-trunk-Java8 - Build # 122 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/122/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 4632 lines...] Tests run: 285, Failures: 0, Errors:

Build failed in Jenkins: Hadoop-Yarn-trunk-Java8 #122

See Changes: [arp] HDFS-7757. Misleading error messages in FSImage.java. (Contributed by Brahma Reddy Battula) [wangda] YARN-3272. Surface container locality info in RM web UI (Jian He via wangda) [stevel] HADOOP-11183. Memor

Hadoop-Yarn-trunk - Build # 856 - Still Failing

See https://builds.apache.org/job/Hadoop-Yarn-trunk/856/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 7315 lines...] Tests run: 285, Failures: 2, Errors: 4, Sk

Build failed in Jenkins: Hadoop-Yarn-trunk #856

See Changes: [arp] HDFS-7757. Misleading error messages in FSImage.java. (Contributed by Brahma Reddy Battula) [wangda] YARN-3272. Surface container locality info in RM web UI (Jian He via wangda) [stevel] HADOOP-11183. Memory-base

Failed: YARN-3249 PreCommit Build #6836

Jira: https://issues.apache.org/jira/browse/YARN-3249 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6836/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-2693 PreCommit Build #6837

Jira: https://issues.apache.org/jira/browse/YARN-2693 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6837/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3136 PreCommit Build #6838

Jira: https://issues.apache.org/jira/browse/YARN-3136 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6838/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3136 PreCommit Build #6839

Jira: https://issues.apache.org/jira/browse/YARN-3136 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6839/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

[jira] [Created] (YARN-3293) Track and display capacity scheduler health metrics in web UI

Varun Vasudev created YARN-3293: --- Summary: Track and display capacity scheduler health metrics in web UI Key: YARN-3293 URL: https://issues.apache.org/jira/browse/YARN-3293 Project: Hadoop YARN

[jira] [Created] (YARN-3294) Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period

Varun Vasudev created YARN-3294: --- Summary: Allow dumping of Capacity Scheduler debug logs via web UI for a fixed time period Key: YARN-3294 URL: https://issues.apache.org/jira/browse/YARN-3294 Project:

Re: Looking to a Hadoop 3 release

Let's not dismiss this quite so handily. Sean, Jason, and Stack replied on HADOOP-11656 pointing out that while we could make classpath isolation opt-in via configuration, what we really want longer term is to have it on by default (or just always on). Stack in particular points out the practical

Failed: YARN-3242 PreCommit Build #6840

Jira: https://issues.apache.org/jira/browse/YARN-3242 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6840/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by

Failed: YARN-2868 PreCommit Build #6841

Jira: https://issues.apache.org/jira/browse/YARN-2868 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6841/ ### ## LAST 60 LINES OF THE CONSOLE ### Started by

Re: Looking to a Hadoop 3 release

In general +1 on 3.0.0. Its time. If we start now, it might make it out by 2016. If we start now, downstreamers can start aligning themselves to land versions that suit at about the same time. While two big items have been called out as possible incompatible changes, and there is ongoing discussio

[jira] [Resolved] (YARN-3031) [Storage abstraction] Create backing storage write interface for ATS writers

[ https://issues.apache.org/jira/browse/YARN-3031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen resolved YARN-3031. --- Resolution: Duplicate Since the patch there covers the code of the writer interface. Let's resolve thi

Failed: YARN-2854 PreCommit Build #6843

Jira: https://issues.apache.org/jira/browse/YARN-2854 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6843/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3264 PreCommit Build #6846

Jira: https://issues.apache.org/jira/browse/YARN-3264 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6846/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3122 PreCommit Build #6845

Jira: https://issues.apache.org/jira/browse/YARN-3122 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6845/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3242 PreCommit Build #6844

Jira: https://issues.apache.org/jira/browse/YARN-3242 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6844/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3267 PreCommit Build #6842

Jira: https://issues.apache.org/jira/browse/YARN-3267 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6842/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

Hi all, I'd like us to revive the effort at https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds being able to work with branches. Having the Jenkins verify patches on branches is very useful even if there may be relaxed review oversight on the said-branch. Unless there a

Failed: YARN-2786 PreCommit Build #6847

### [...truncated 36 lines...] First, rewinding head to replay your work on top of it... Fast-forwarded trunk to ed70fa142cabdbc1065e4dbbc95e99c8850c4751. YARN-2786 patch is being downloaded at Wed Mar 4 21:30:23 UTC 2015 from http://issues.apache.org/jira/secure/attachment/12702610/YARN-2786-20150304-1-branch2

Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

Thanks for reviving this on email, Vinod. Newer folks like me might not be aware of this JIRA/effort. This would be wonderful to have so (1) we know the status of release branches (branch-2, etc.) and also (2) feature branches (YARN-2928). Jonathan's or Matt's proposal for including branch name lo

Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

+1 If we can make things look like HBase support for precommit testing on branches (HBASE-12944), that would make it easier for new and occasional contributors who might end up working in other ecosystem projects. AFAICT, Jonathan's proposal for branch names in patch names does this. On Wed, Ma

Failed: YARN-2786 PreCommit Build #6848

### [...truncated 3253 lines...] {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12702617/YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch against trunk revision ed70fa1. {color:green}+1 @author{color}. The patch

Failed: YARN-2786 PreCommit Build #6851

### [...truncated 36 lines...] First, rewinding head to replay your work on top of it... Fast-forwarded trunk to c66c3ac6bf9f63177279feec3f2917e4b882e2bc. YARN-2786 patch is being downloaded at Wed Mar 4 22:56:46 UTC 2015 from http://issues.apache.org/jira/secure/attachment/12702629/YARN-2786-20150304-2-branch2

RE: 2.7 status

Thanks Vinod for the hints. I have updated the both patches aligning with latest codes, and added more unit tests. The building results look reasonable. Thanks anyone that would give them more review and I would update in timely manner. Regards, Kai -Original Message- From: Vinod Kum

Re: Reviving HADOOP-7435: Making Jenkins pre-commit build work with branches

+1. It¹s really helpful for branch development. To continue Karthik¹s point, is it good make pre-commit testing against branch-2 as the default too like that against trunk? On 3/4/15, 1:47 PM, "Sean Busbey" wrote: >+1 > >If we can make things look like HBase support for precommit testing on >bra

Failed: YARN-2786 PreCommit Build #6852

### [...truncated 36 lines...] First, rewinding head to replay your work on top of it... Fast-forwarded trunk to 722b4794693d8bad1dee0ca5c2f99030a08402f9. YARN-2786 patch is being downloaded at Wed Mar 4 23:51:42 UTC 2015 from http://issues.apache.org/jira/secure/attachment/12702629/YARN-2786-20150304-2-branch2

RE: Looking to a Hadoop 3 release

Might I have some comments for this, just providing my thought. Thanks. >> If we start now, it might make it out by 2016. If we start now, >> downstreamers can start aligning themselves to land versions that suit at >> about the same time. Not only for down streamers to align with the long term

Re: Looking to a Hadoop 3 release

On Wed, Mar 4, 2015 at 10:46 AM, Stack wrote: > In general +1 on 3.0.0. Its time. If we start now, it might make it out by > 2016. If we start now, downstreamers can start aligning themselves to land > versions that suit at about the same time. > > While two big items have been called out as poss

Failed: YARN-3267 PreCommit Build #6849

Jira: https://issues.apache.org/jira/browse/YARN-3267 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6849/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3275 PreCommit Build #6850

Jira: https://issues.apache.org/jira/browse/YARN-3275 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6850/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Success: YARN-3122 PreCommit Build #6853

Jira: https://issues.apache.org/jira/browse/YARN-3122 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6853/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

[jira] [Created] (YARN-3295) Fix documentation nits found in markdown conversion

Masatake Iwasaki created YARN-3295: -- Summary: Fix documentation nits found in markdown conversion Key: YARN-3295 URL: https://issues.apache.org/jira/browse/YARN-3295 Project: Hadoop YARN Iss

Failed: YARN-3264 PreCommit Build #6855

Jira: https://issues.apache.org/jira/browse/YARN-3264 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6855/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Success: YARN-2786 PreCommit Build #6854

### [...truncated 3251 lines...] {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12702659/YARN-2786-20150304-2-trunk-to-kick-jenkins.patch against trunk revision 722b479. {color:green}+1 @author{color}. The

Re: Looking to a Hadoop 3 release

One of the questions that keeps popping up is “what exactly is in trunk?” As some may recall, I had done some experiments creating the change log based upon JIRA. While the interest level appeared to be approaching zero, I kept playing with it a bit and eventually also started playing with the

Failed: YARN-3264 PreCommit Build #6857

Jira: https://issues.apache.org/jira/browse/YARN-3264 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6857/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3264 PreCommit Build #6862

Jira: https://issues.apache.org/jira/browse/YARN-3264 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6862/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-1809 PreCommit Build #6859

Jira: https://issues.apache.org/jira/browse/YARN-1809 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6859/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3243 PreCommit Build #6863

Jira: https://issues.apache.org/jira/browse/YARN-3243 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6863/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-2190 PreCommit Build #6861

Jira: https://issues.apache.org/jira/browse/YARN-2190 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6861/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat

Failed: YARN-3154 PreCommit Build #6860

Jira: https://issues.apache.org/jira/browse/YARN-3154 Build: https://builds.apache.org/job/PreCommit-YARN-Build/6860/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncat