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

See Changes: [Arun Suresh] YARN-5176. More test cases for queuing of containers at the NM. -- [...truncated 29396 lines...] Generating

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

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1552/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 29593 lines...] [INFO] Reactor Summary: [INFO] [IN

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

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1551/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 34367 lines...] [INFO] Reactor Summary: [INFO] [IN

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

See Changes: [rkanter] MAPREDUCE-6702. TestMiniMRChildTask.testTaskEnv and [Arun Suresh] Addendum patch for YARN-5180 updating findbugs-exclude.xml [xgong] YARN-5199. Close LogReader in in AHSWebServices#getStreamingOutput and

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

See Changes: [wangda] YARN-4837. User facing aspects of 'AM blacklisting' feature need fixing. -- [...truncated 29427 lines...] [WARNING] ^ [WARNING]

Hadoop-Yarn-trunk-Java8 - Build # 1550 - Failure

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1550/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 29624 lines...] [ERROR] For more information about

[jira] [Resolved] (YARN-5180) Allow ResourceRequest to specify an enforceExecutionType flag

[ https://issues.apache.org/jira/browse/YARN-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh resolved YARN-5180. --- Resolution: Fixed Committed addendum patch to trunk and branch-2 > Allow ResourceRequest to specify an

Re: Cannot create release artifacts for branch-2.8

It's also the best option to fix create-release. If we cannot get help to fix the script, it seems the only choice is to maintain CHANGES.txt again in branch-2. On Tue, Jun 7, 2016 at 2:56 PM, Andrew Wang wrote: > I'm not super happy about the alternative of reverting the auto-generated > CHANGE

Re: Cannot create release artifacts for branch-2.8

I'm not super happy about the alternative of reverting the auto-generated CHANGES/RL JIRAs, since it means we have to do CHANGES.txt maintenance again in branch-2. That's an overhead that we pay for every commit, and it's particularly bad when doing backports. As I commented on HADOOP-12892, I thi

Re: Cannot create release artifacts for branch-2.8

> > I'm not the one who cherry-picked them into branch-2, so I don't > care either way. I've been extremely open about targeting my code for the > past three years for trunk. With few exceptions, I generally only commit > code I write or even review to branch-2 if someone practically begs

Re: Cannot create release artifacts for branch-2.8

> On Jun 7, 2016, at 1:44 PM, Wangda Tan wrote: > > That gonna be very helpful, but I guess it only works on trunk, correct? At > least many of the parameters you mentioned are not in create-release.sh of > branch-2. Yup. create-release was rewritten in trunk. The previous version had

Re: Cannot create release artifacts for branch-2.8

+ Andrew/Akira On Tue, Jun 7, 2016 at 1:44 PM, Wangda Tan wrote: > That gonna be very helpful, but I guess it only works on trunk, correct? > At least many of the parameters you mentioned are not in create-release.sh > of branch-2. > > We may need to make a decision for this in branch-2. Honestl

Re: Cannot create release artifacts for branch-2.8

That gonna be very helpful, but I guess it only works on trunk, correct? At least many of the parameters you mentioned are not in create-release.sh of branch-2. We may need to make a decision for this in branch-2. Honestly, I have little understanding about shell script related stuffs, if I cannot

[jira] [Created] (YARN-5212) Run existing ContainerManager tests using QueuingContainerManagerImpl

Konstantinos Karanasos created YARN-5212: Summary: Run existing ContainerManager tests using QueuingContainerManagerImpl Key: YARN-5212 URL: https://issues.apache.org/jira/browse/YARN-5212 Pro

Jenkins build is back to normal : Hadoop-Yarn-trunk-Java8 #1549

See - To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Re: Why there are so many revert operations on trunk?

Lolz! Thanks for your opinion Larry. I have often seen "-1 until this is done according to my way rather than your way" (obviously not in those words), even when both ways are perfectly reasonable. Anyway, I didn't expect the voting rules to change. :-) Cheers Ravi On Tue, Jun 7, 2016 at 11:02 A

[jira] [Created] (YARN-5211) Supporting "priorities" in the ReservationSystem

Carlo Curino created YARN-5211: -- Summary: Supporting "priorities" in the ReservationSystem Key: YARN-5211 URL: https://issues.apache.org/jira/browse/YARN-5211 Project: Hadoop YARN Issue Type: Su

Re: Cannot create release artifacts for branch-2.8

> On Jun 7, 2016, at 11:37 AM, Wangda Tan wrote: > > I have tested both, create-releases fails on my local box as well. > > According to the link you provided, we probably need to update how to > release wiki > . I'm working on

Re: Cannot create release artifacts for branch-2.8

I have tested both, create-releases fails on my local box as well. According to the link you provided, we probably need to update how to release wiki . On Tue, Jun 7, 2016 at 6:22 AM, Allen Wittenauer wrote: > > > On Jun 6, 2016,

[jira] [Created] (YARN-5210) NPE in Distributed Shell while publishing DS_CONTAINER_START event and other miscellaneous issues

Varun Saxena created YARN-5210: -- Summary: NPE in Distributed Shell while publishing DS_CONTAINER_START event and other miscellaneous issues Key: YARN-5210 URL: https://issues.apache.org/jira/browse/YARN-5210

Re: Why there are so many revert operations on trunk?

-1 needs not be a taken as a derogatory statement being a number should actually make it less emotional. It is dangerous to a community to become oversensitive to it. I generally see language such as "I am -1 on this until this particular thing is fixed" or that it violates some common pattern or

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

See Changes: [junping_du] HADOOP-10048. LocalDirAllocator should avoid holding locks while -- [...truncated 34177 lines...] Generating

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

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1548/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 34374 lines...] [INFO] Reactor Summary: [INFO] [IN

Re: Why there are so many revert operations on trunk?

+1 on being more respectful. We seem to be having a lot of distasteful discussions recently. If we fight each other, we are only helping our competitors win (and trust me, its out there). I would also respectfully request people not to throw -1s around. I have faced this a few times and its really

Re: Why there are so many revert operations on trunk?

- We need to at the least force a reset of expectations w.r.t how trunk and small / medium / incompatible changes there are treated. We should hold off making a release off trunk before this gets fully discussed in the community and we all reach a consensus. +1. We should hold off any release w

[jira] [Created] (YARN-5209) Transmission ContainerExecutor Parameters By The Client

zhangyubiao created YARN-5209: - Summary: Transmission ContainerExecutor Parameters By The Client Key: YARN-5209 URL: https://issues.apache.org/jira/browse/YARN-5209 Project: Hadoop YARN Issue Typ

Re: Cannot create release artifacts for branch-2.8

> On Jun 6, 2016, at 10:50 PM, Wangda Tan wrote: > > Hi Hadoop Devs, > > As you know, we're pushing 2.8.0 releases recently, there're couple of > issues that block creating release artifacts from source code. > > I tried following approaches: > 1) Run build through Hadoop Jenkins Job: http:/

[jira] [Created] (YARN-5208) Run all tests with security.token.service.use_ip enabled

Rohith Sharma K S created YARN-5208: --- Summary: Run all tests with security.token.service.use_ip enabled Key: YARN-5208 URL: https://issues.apache.org/jira/browse/YARN-5208 Project: Hadoop YARN

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

See Changes: [aajisaka] HDFS-10485. Fix findbugs warning in FSEditLog.java. (aajisaka) -- [...truncated 34177 lines...] Generating

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

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1547/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 34374 lines...] [INFO] Reactor Summary: [INFO] [IN

[jira] [Created] (YARN-5207) Web-Proxy should support multi-homed systems.

Zephyr Guo created YARN-5207: Summary: Web-Proxy should support multi-homed systems. Key: YARN-5207 URL: https://issues.apache.org/jira/browse/YARN-5207 Project: Hadoop YARN Issue Type: New Featu

[jira] [Created] (YARN-5206) RegistrySecurity includes id:pass in exception text if considered invalid

Steve Loughran created YARN-5206: Summary: RegistrySecurity includes id:pass in exception text if considered invalid Key: YARN-5206 URL: https://issues.apache.org/jira/browse/YARN-5206 Project: Hadoop

Re: Why there are so many revert operations on trunk?

+1 This is a good summary, And we are better off resolving issues through discussions on emails, rather than JIRA, and everyone behaving amicably towards each other. I think we should be more willing to do feature branches, especially for things like - anything deep into the codebase - self

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

See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1546/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 34374 lines...] [INFO] Reactor Summary: [INFO] [IN

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

See Changes: [rohithsharmaks] YARN-5118. Tests fails with localizer port bind exception. Contributed -- [...truncated 34177 lines...] Generating