Failed: YARN-1964 PreCommit Build #5194

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1964
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5194/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3476 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672275/YARN-1964.patch
  against trunk revision 17d1202.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5194//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5194//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
87a31f58428a4eefdded244eb39615d8a8ae45a1 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 25 artifacts
Archive block size is 32768
Received 0 blocks and 9138615 bytes
Compression is 0.0%
Took 5 sec
Description set: YARN-1964
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Re: Calling a merge vote for YARN-1051

[Thomas Jungblut]

+1 (non-binding)
Thanks for adding this, really useful feature.

On 30 September 2014 19:40, Chris Douglas  wrote:

> +1
>
> Excellent work, Carlo and Subru. -C
>
> On Fri, Sep 26, 2014 at 11:50 AM, Carlo Curino 
> wrote:
> > (Apologies if it is delivered twice.)
> >
> > YARN Devs,
> >
> > We propose to merge YARN-1051 development branch into trunk.
> >
> > Key Idea:
> > This work adds support for Reservations to YARN RM. The key idea is to
> allow users to request dedicated access to resources (a reservation), ahead
> of time.
> > For example I can ask for "10 containers for 1 hour sometime between 4pm
> and 9pm today".  The RM keeps track of the accepted reservation by means of
> > a Plan (think it as an agenda on how the  cluster resources will be
> used), and performs admission control to guarantee that if a reservation is
> accepted enough
> > resources are set aside to satisfy it.  We enforce the reservation
> promises by dynamically creating/resizing/removing queues at the right
> time. This allows us
> > to leverage the existing schedulers for the actual container assignment
> and tracking. The key benefit is to expose to the scheduler flexibility of
> allocation, while
> > guaranteeing users predictable resource allocation.
> >
> > Status
> >
> > * The work has been "broken down" into 14 subtasks (+3 patches
> already committed to trunk for move/kill of apps). All the issues have been
> resolved.
> >
> > * Jenkins +1 the patch (with the exception of one test failure
> which we did not introduce, which is tracked here:
> https://issues.apache.org/jira/browse/MAPREDUCE-6094)
> >
> > * Simple integration with MapReduce:
> https://issues.apache.org/jira/browse/MAPREDUCE-6103
> >
> > * The broken-down patches have been reviewed and +1ed by Vinod
> Kumar Vavilapali, Jian He, Wangda Tan, Karthik Kambatla, and Chris Douglas.
> Thanks to all of you for the thorough reviews!
> >
> > * The current version has been rather thoroughly tested by
> running it on our 250 machines research cluster for months (first prototype
> was operational about a year ago) by:
> >
> > o   Running hundreds of thousands of job generate by a modified version
> of gridmix that exercise the reservations mechanism side-by-side normal
> queues.
> >
> > o   To support our integration with the resource estimation framework
> Perforator (http://research.microsoft.com/pubs/178971/perforator.pdf).
> Kaushik and Dharmesh have been pounding the reservation system for their
> research for 3-4 months now, and helped us spot few bugs and iron them out.
> >
> > o   Code has been inspected/extended by 4-5 other researchers which are
> exploring integration with other systems and extensions of our algorithms
> for "reservation placement".
> >
> > * We have few ideas for follow-up extensions/improvements are
> tracked by the umbrella JIRA
> https://issues.apache.org/jira/browse/YARN-2572
> >
> > Documents and Deliverables
> >
> > * This work was accepted for publication to SoCC 2014
> (pre-camera ready version of the paper here):
> https://issues.apache.org/jira/secure/attachment/12671498/socc14-paper15.pdf
> >
> > * Shorter design doc:
> https://issues.apache.org/jira/secure/attachment/12628330/YARN-1051-design.pdf
> >
> > * Overall patch:
> https://issues.apache.org/jira/secure/attachment/12671361/YARN-1051.1.patch
> >
> > * Per Karthik request we are preparing a small how-to document
> and example code/configuration tracked by
> https://issues.apache.org/jira/browse/YARN-2609
> >
> >
> > Credits
> > Myself and Subru did lots of the coding (hence the flow of patches from
> us), but this is a group effort that could have not been possible without
> the ideas and hard work of many other
> > folks in our research group (Microsoft-CISL). Major kudos to:  Chris
> Douglas, Sriram Rao, Raghu Ramakrishnan, and our intern Djellel Difallah.
> Also big thanks to the many folks in community  (Arun, Vinod, Alejandro,
> Bikas, Karthik, Sandy, Hitesh, Jakob, Mohammad, Mayank, Jason, Bobby, and
> many more) that helped us shape our ideas and code with very insightful
> feedback and comments.
> >
> > We expect the vote to run for the usual 7 days and will expire at 12pm
> PDT on Oct 3. Please feel free to reach out to us if you have any
> questions/doubts.
> >
> > Cheers,
> > Carlo & Subru
> >
>

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

[Apache Jenkins Server]

See https://builds.apache.org/job/Hadoop-Yarn-trunk/697/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 9029 lines...]
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-yarn ... SUCCESS [  3.145 s]
[INFO] hadoop-yarn-api ... SUCCESS [02:10 min]
[INFO] hadoop-yarn-common  SUCCESS [02:09 min]
[INFO] hadoop-yarn-server  SUCCESS [  0.087 s]
[INFO] hadoop-yarn-server-common . SUCCESS [ 36.581 s]
[INFO] hadoop-yarn-server-nodemanager  SUCCESS [05:03 min]
[INFO] hadoop-yarn-server-web-proxy .. SUCCESS [ 21.435 s]
[INFO] hadoop-yarn-server-applicationhistoryservice .. SUCCESS [02:16 min]
[INFO] hadoop-yarn-server-resourcemanager  SUCCESS [34:09 min]
[INFO] hadoop-yarn-server-tests .. SUCCESS [02:10 min]
[INFO] hadoop-yarn-client  SUCCESS [06:42 min]
[INFO] hadoop-yarn-server-sharedcachemanager . SUCCESS [  7.572 s]
[INFO] hadoop-yarn-applications .. SUCCESS [  0.046 s]
[INFO] hadoop-yarn-applications-distributedshell . FAILURE [05:13 min]
[INFO] hadoop-yarn-applications-unmanaged-am-launcher  SKIPPED
[INFO] hadoop-yarn-site .. SKIPPED
[INFO] hadoop-yarn-project ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:01 h
[INFO] Finished at: 2014-10-01T11:36:59+00:00
[INFO] Final Memory: 88M/858M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on 
project hadoop-yarn-applications-distributedshell: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/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  -rf :hadoop-yarn-applications-distributedshell
Build step 'Execute shell' marked build as failure
Archiving artifacts
Updating YARN-1492
Updating YARN-2179
Updating HADOOP-11154
Updating HADOOP-11156
Updating HADOOP-11145
Updating YARN-2610
Updating HADOOP-3
Updating YARN-2602
Updating YARN-2387
Updating HADOOP-7
Updating HDFS-7167
Updating YARN-2594
Updating YARN-2627
Updating HDFS-7153
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

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

[Apache Jenkins Server]

See 

Changes:

[cnauroth] HADOOP-11154. Update BUILDING.txt to state that CMake 3.0 or newer 
is required on Mac. Contributed by Chris Nauroth.

[cnauroth] HADOOP-11145. TestFairCallQueue fails. Contributed by Akira AJISAKA.

[acmurthy] Preparing to branch hadoop-2.6

[jing9] HDFS-7167. NPE while running Mover if the given path is for a file. 
Contributed by Jing Zhao.

[kasha] YARN-2610. Hamlet should close table tags. (Ray Chiang via kasha)

[zjshen] YARN-2627. Added the info logs of attemptFailuresValidityInterval and 
number of previous failed attempts. Contributed by Xuan Gong.

[jlowe] YARN-2387. Resource Manager crashes with NPE due to lack of 
synchronization. Contributed by Mit Desai

[kasha] YARN-2594. Potential deadlock in RM when querying 
ApplicationResourceUsageReport. (Wangda Tan via kasha)

[wang] HADOOP-11156. DelegateToFileSystem should implement getFsStatus(final 
Path f). Contributed by Zhihai Xu.

[jianhe] YARN-2602. Fixed possible NPE in 
ApplicationHistoryManagerOnTimelineStore. Contributed by Zhijie Shen

[wang] HADOOP-3. Namenode not able to reconnect to KMS after KMS restart. 
(Arun Suresh via wang)

[stevel] HADOOP-7 UGI HadoopLoginModule doesn't catch & wrap all 
kerberos-related exceptions (stevel)

[arp] HDFS-7153. Add storagePolicy to NN edit log during file creation. (Arpit 
Agarwal)

[kasha] YARN-2179. [YARN-1492] Initial cache manager structure and context. 
(Chris Trezzo via kasha)

--
[...truncated 8836 lines...]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (create-testdirs) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Executing tasks

main:
[mkdir] Created dir: 

[INFO] Executed tasks
[INFO] 
[INFO] --- maven-resources-plugin:2.2:resources (default-resources) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Using default encoding to copy filtered resources.
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Compiling 3 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.2:testResources (default-testResources) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Using default encoding to copy filtered resources.
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:test-jar (default) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.16:test (default-test) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---
Running org.apache.hadoop.yarn.server.sharedcachemanager.TestRemoteAppChecker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.551 sec - in 
org.apache.hadoop.yarn.server.sharedcachemanager.TestRemoteAppChecker

Results :

Tests run: 2, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar-no-fork (hadoop-java-sources) @ 
hadoop-yarn-server-sharedcachemanager ---
[INFO] Building jar: 

[jira] [Created] (YARN-2633) TestContainerLauncherImpl sometimes fails

[Mit Desai (JIRA)]

Mit Desai created YARN-2633:
---

 Summary: TestContainerLauncherImpl sometimes fails
 Key: YARN-2633
 URL: https://issues.apache.org/jira/browse/YARN-2633
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Mit Desai
Assignee: Mit Desai


{noformat}
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: 
java.lang.NoSuchMethodException: 
org.apache.hadoop.yarn.api.ContainerManagementProtocol$$EnhancerByMockitoWithCGLIB$$25708415.close()
at java.lang.Class.getMethod(Class.java:1665)
at 
org.apache.hadoop.yarn.factories.impl.pb.RpcClientFactoryPBImpl.stopClient(RpcClientFactoryPBImpl.java:90)
at 
org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC.stopProxy(HadoopYarnProtoRPC.java:54)
at 
org.apache.hadoop.yarn.client.api.impl.ContainerManagementProtocolProxy.mayBeCloseProxy(ContainerManagementProtocolProxy.java:79)
at 
org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl$Container.kill(ContainerLauncherImpl.java:225)
at 
org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl.shutdownAllContainers(ContainerLauncherImpl.java:320)
at 
org.apache.hadoop.mapreduce.v2.app.launcher.ContainerLauncherImpl.serviceStop(ContainerLauncherImpl.java:331)
at 
org.apache.hadoop.service.AbstractService.stop(AbstractService.java:221)
at 
org.apache.hadoop.mapreduce.v2.app.launcher.TestContainerLauncherImpl.testMyShutdown(TestContainerLauncherImpl.java:315)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2180 PreCommit Build #5195

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2180
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5195/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3268 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12672206/YARN-2180-trunk-v6.patch
  against trunk revision 17d1202.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-sharedcachemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5195//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5195//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
c906c40139bda3824ef87bb089e5a8bbed456997 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 25 artifacts
Archive block size is 32768
Received 0 blocks and 8984460 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-2180
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2634) Test failure for TestClientRMTokens

[Junping Du (JIRA)]

Junping Du created YARN-2634:


 Summary: Test failure for TestClientRMTokens
 Key: YARN-2634
 URL: https://issues.apache.org/jira/browse/YARN-2634
 Project: Hadoop YARN
  Issue Type: Test
Reporter: Junping Du


The test get failed as below:
{noformat}
---
Test set: org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens
---
Tests run: 6, Failures: 3, Errors: 2, Skipped: 0, Time elapsed: 60.184 sec <<< 
FAILURE! - in org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens
testShortCircuitRenewCancelDifferentHostSamePort(org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens)
  Time elapsed: 22.693 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.checkShortCircuitRenewCancel(TestClientRMTokens.java:319)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.testShortCircuitRenewCancelDifferentHostSamePort(TestClientRMTokens.java:272)

testShortCircuitRenewCancelDifferentHostDifferentPort(org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens)
  Time elapsed: 20.087 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.checkShortCircuitRenewCancel(TestClientRMTokens.java:319)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.testShortCircuitRenewCancelDifferentHostDifferentPort(TestClientRMTokens.java:283)

testShortCircuitRenewCancel(org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens)
  Time elapsed: 0.031 sec  <<< ERROR!
java.lang.NullPointerException: null
at 
org.apache.hadoop.yarn.security.client.RMDelegationTokenIdentifier$Renewer.getRmClient(RMDelegationTokenIdentifier.java:148)
at 
org.apache.hadoop.yarn.security.client.RMDelegationTokenIdentifier$Renewer.renew(RMDelegationTokenIdentifier.java:101)
at org.apache.hadoop.security.token.Token.renew(Token.java:377)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.checkShortCircuitRenewCancel(TestClientRMTokens.java:309)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.testShortCircuitRenewCancel(TestClientRMTokens.java:241)

testShortCircuitRenewCancelSameHostDifferentPort(org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens)
  Time elapsed: 0.061 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.checkShortCircuitRenewCancel(TestClientRMTokens.java:319)
at 
org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens.testShortCircuitRenewCancelSameHostDifferentPort(TestClientRMTokens.java:261)

testShortCircuitRenewCancelWildcardAddress(org.apache.hadoop.yarn.server.resourcemanager.TestClientRMTokens)
  Time elapsed: 0.07 sec  <<< ERROR!
java.lang.NullPointerException: null
at org.apache.hadoop.net.NetUtils.isLocalAddress(NetUtils.java:684)
at 
org.apache.hadoop.yarn.security.client.RMDelegationTokenIdentifier$Renewer.getRmClient(RMDelegationTokenIdentifier.java:149)

   
1,1   Top

{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2615 PreCommit Build #5196

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2615
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5196/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 4599 lines...]

{color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-common-project/hadoop-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  org.apache.hadoop.crypto.random.TestOsSecureRandom
  org.apache.hadoop.ha.TestZKFailoverControllerStress
  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore
  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestZKRMStateStore

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5196//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5196//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5196//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
7b44be4385b4f9178d8eb3785d447da46d71f00f logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 23 artifacts
Archive block size is 32768
Received 0 blocks and 8424023 bytes
Compression is 0.0%
Took 2.6 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2635) TestRMRestart fails with FairScheduler

[Wei Yan (JIRA)]

Wei Yan created YARN-2635:
-

 Summary: TestRMRestart fails with FairScheduler
 Key: YARN-2635
 URL: https://issues.apache.org/jira/browse/YARN-2635
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Wei Yan
Assignee: Wei Yan


If we change the scheduler from Capacity Scheduler to Fair Scheduler, the 
TestRMRestart would fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-1063 PreCommit Build #5197

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1063
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5197/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 4160 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12657587/YARN-1063.6.patch
  against trunk revision 04b0843.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5197//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5197//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
09e0697dc2659e8d3c7f2e9afef8a371b49e991d logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 12 artifacts
Archive block size is 32768
Received 0 blocks and 8570935 bytes
Compression is 0.0%
Took 2.9 sec
Description set: YARN-1063
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1972 PreCommit Build #5200

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1972
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5200/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 22 lines...]

==
==
Testing patch for YARN-1972.
==
==


HEAD is now at 1f5b42a HDFS-7158. Reduce the memory usage of WebImageViewer. 
Contributed by Haohui Mai.
Previous HEAD position was 1f5b42a... HDFS-7158. Reduce the memory usage of 
WebImageViewer. Contributed by Haohui Mai.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 96 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 1f5b42ac4881b734c799bfb527884c0d117929bd.
YARN-1972 patch is being downloaded at Wed Oct  1 18:31:08 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12672375/YARN-1972.delta.5-branch-2.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12672375/YARN-1972.delta.5-branch-2.patch
  against trunk revision 1f5b42a.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5200//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
1fcb5212a3bb4db283ed887ba5ca5616fe3045fd logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1879 PreCommit Build #5198

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1879
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5198/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3424 lines...]

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  org.apache.hadoop.yarn.client.TestResourceTrackerOnHA
  
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5198//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5198//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5198//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
b7a93331945dc1a6196a91ac7625f5fe71a2e307 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 26 artifacts
Archive block size is 32768
Received 0 blocks and 8148801 bytes
Compression is 0.0%
Took 3.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2630 PreCommit Build #5199

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2630
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5199/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3644 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672368/YARN-2630.3.patch
  against trunk revision 1f5b42a.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5199//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5199//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5199//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
3f1e084873a70cbb1b37b8204664c6211d6eec37 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 31 artifacts
Archive block size is 32768
Received 0 blocks and 8137249 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2630 PreCommit Build #5201

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2630
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5201/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3571 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672374/YARN-2630.4.patch
  against trunk revision 1f5b42a.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The test build failed in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
 

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5201//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5201//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5201//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
1c8e9f4880993cdda82ece19a9eb4bf6717619c9 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 36 artifacts
Archive block size is 32768
Received 0 blocks and 9545640 bytes
Compression is 0.0%
Took 3.1 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2636) Windows Secure Container Executor: add unit tests for WSCE

[Remus Rusanu (JIRA)]

Remus Rusanu created YARN-2636:
--

 Summary: Windows Secure Container Executor: add unit tests for WSCE
 Key: YARN-2636
 URL: https://issues.apache.org/jira/browse/YARN-2636
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Remus Rusanu
Assignee: Remus Rusanu
Priority: Critical


As title says.

The WSCE has no check-in unit tests. Much of the functionality depends on 
elevated hadoopwinutilsvc service and cannot be tested, but lets test what is 
possible to be mocked in Java.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2408 PreCommit Build #5203

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2408
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5203/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 22 lines...]

==
==
Testing patch for YARN-2408.
==
==


HEAD is now at 1f5b42a HDFS-7158. Reduce the memory usage of WebImageViewer. 
Contributed by Haohui Mai.
Previous HEAD position was 1f5b42a... HDFS-7158. Reduce the memory usage of 
WebImageViewer. Contributed by Haohui Mai.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 1f5b42ac4881b734c799bfb527884c0d117929bd.
YARN-2408 patch is being downloaded at Wed Oct  1 19:50:19 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12672388/YARN-2408.4.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672388/YARN-2408.4.patch
  against trunk revision 1f5b42a.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5203//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
893a713c5f7c8fa7ce07c22fc9bb16ea3195a781 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2628 PreCommit Build #5202

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2628
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5202/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3185 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12672381/apache-yarn-2628.0.patch
  against trunk revision 1f5b42a.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5202//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5202//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5202//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
b30a5df984ff4cd587dec7cc9dbdf5b34b539799 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 16 artifacts
Archive block size is 32768
Received 0 blocks and 7771404 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Re: Calling a merge vote for YARN-1051

[Jian He]

+1,

Carlo and Subru,  great job !  thanks for your contribution !
I reviewed a couple of CapacityScheduler related patches, they are in good
shape. In the minimum, they are not affecting existing behavior. should be
safe to merge.

Jian


On Wed, Oct 1, 2014 at 2:46 AM, Thomas Jungblut 
wrote:

> +1 (non-binding)
> Thanks for adding this, really useful feature.
>
> On 30 September 2014 19:40, Chris Douglas  wrote:
>
> > +1
> >
> > Excellent work, Carlo and Subru. -C
> >
> > On Fri, Sep 26, 2014 at 11:50 AM, Carlo Curino 
> > wrote:
> > > (Apologies if it is delivered twice.)
> > >
> > > YARN Devs,
> > >
> > > We propose to merge YARN-1051 development branch into trunk.
> > >
> > > Key Idea:
> > > This work adds support for Reservations to YARN RM. The key idea is to
> > allow users to request dedicated access to resources (a reservation),
> ahead
> > of time.
> > > For example I can ask for "10 containers for 1 hour sometime between
> 4pm
> > and 9pm today".  The RM keeps track of the accepted reservation by means
> of
> > > a Plan (think it as an agenda on how the  cluster resources will be
> > used), and performs admission control to guarantee that if a reservation
> is
> > accepted enough
> > > resources are set aside to satisfy it.  We enforce the reservation
> > promises by dynamically creating/resizing/removing queues at the right
> > time. This allows us
> > > to leverage the existing schedulers for the actual container assignment
> > and tracking. The key benefit is to expose to the scheduler flexibility
> of
> > allocation, while
> > > guaranteeing users predictable resource allocation.
> > >
> > > Status
> > >
> > > * The work has been "broken down" into 14 subtasks (+3 patches
> > already committed to trunk for move/kill of apps). All the issues have
> been
> > resolved.
> > >
> > > * Jenkins +1 the patch (with the exception of one test failure
> > which we did not introduce, which is tracked here:
> > https://issues.apache.org/jira/browse/MAPREDUCE-6094)
> > >
> > > * Simple integration with MapReduce:
> > https://issues.apache.org/jira/browse/MAPREDUCE-6103
> > >
> > > * The broken-down patches have been reviewed and +1ed by Vinod
> > Kumar Vavilapali, Jian He, Wangda Tan, Karthik Kambatla, and Chris
> Douglas.
> > Thanks to all of you for the thorough reviews!
> > >
> > > * The current version has been rather thoroughly tested by
> > running it on our 250 machines research cluster for months (first
> prototype
> > was operational about a year ago) by:
> > >
> > > o   Running hundreds of thousands of job generate by a modified version
> > of gridmix that exercise the reservations mechanism side-by-side normal
> > queues.
> > >
> > > o   To support our integration with the resource estimation framework
> > Perforator (http://research.microsoft.com/pubs/178971/perforator.pdf).
> > Kaushik and Dharmesh have been pounding the reservation system for their
> > research for 3-4 months now, and helped us spot few bugs and iron them
> out.
> > >
> > > o   Code has been inspected/extended by 4-5 other researchers which are
> > exploring integration with other systems and extensions of our algorithms
> > for "reservation placement".
> > >
> > > * We have few ideas for follow-up extensions/improvements are
> > tracked by the umbrella JIRA
> > https://issues.apache.org/jira/browse/YARN-2572
> > >
> > > Documents and Deliverables
> > >
> > > * This work was accepted for publication to SoCC 2014
> > (pre-camera ready version of the paper here):
> >
> https://issues.apache.org/jira/secure/attachment/12671498/socc14-paper15.pdf
> > >
> > > * Shorter design doc:
> >
> https://issues.apache.org/jira/secure/attachment/12628330/YARN-1051-design.pdf
> > >
> > > * Overall patch:
> >
> https://issues.apache.org/jira/secure/attachment/12671361/YARN-1051.1.patch
> > >
> > > * Per Karthik request we are preparing a small how-to document
> > and example code/configuration tracked by
> > https://issues.apache.org/jira/browse/YARN-2609
> > >
> > >
> > > Credits
> > > Myself and Subru did lots of the coding (hence the flow of patches from
> > us), but this is a group effort that could have not been possible without
> > the ideas and hard work of many other
> > > folks in our research group (Microsoft-CISL). Major kudos to:  Chris
> > Douglas, Sriram Rao, Raghu Ramakrishnan, and our intern Djellel Difallah.
> > Also big thanks to the many folks in community  (Arun, Vinod, Alejandro,
> > Bikas, Karthik, Sandy, Hitesh, Jakob, Mohammad, Mayank, Jason, Bobby, and
> > many more) that helped us shape our ideas and code with very insightful
> > feedback and comments.
> > >
> > > We expect the vote to run for the usual 7 days and will expire at 12pm
> > PDT on Oct 3. Please feel free to reach out to us if you have any
> > questions/doubts.
> > >
> > > Cheers,
> > > Carlo & Subru
> > >
> >
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended fo

Re: Calling a merge vote for YARN-1051

[Wangda Tan]

+1 (non-binding),
Reviewed several patches related to scheduler side changes. As Jian
mentioned, this will not affect existing behavior.
Looking forward this feature will be used by more people. Thanks for Carlo
and Subru!

Thanks,
Wangda

On Wed, Oct 1, 2014 at 1:21 PM, Jian He  wrote:

> +1,
>
> Carlo and Subru,  great job !  thanks for your contribution !
> I reviewed a couple of CapacityScheduler related patches, they are in good
> shape. In the minimum, they are not affecting existing behavior. should be
> safe to merge.
>
> Jian
>
>
> On Wed, Oct 1, 2014 at 2:46 AM, Thomas Jungblut 
> wrote:
>
> > +1 (non-binding)
> > Thanks for adding this, really useful feature.
> >
> > On 30 September 2014 19:40, Chris Douglas  wrote:
> >
> > > +1
> > >
> > > Excellent work, Carlo and Subru. -C
> > >
> > > On Fri, Sep 26, 2014 at 11:50 AM, Carlo Curino 
> > > wrote:
> > > > (Apologies if it is delivered twice.)
> > > >
> > > > YARN Devs,
> > > >
> > > > We propose to merge YARN-1051 development branch into trunk.
> > > >
> > > > Key Idea:
> > > > This work adds support for Reservations to YARN RM. The key idea is
> to
> > > allow users to request dedicated access to resources (a reservation),
> > ahead
> > > of time.
> > > > For example I can ask for "10 containers for 1 hour sometime between
> > 4pm
> > > and 9pm today".  The RM keeps track of the accepted reservation by
> means
> > of
> > > > a Plan (think it as an agenda on how the  cluster resources will be
> > > used), and performs admission control to guarantee that if a
> reservation
> > is
> > > accepted enough
> > > > resources are set aside to satisfy it.  We enforce the reservation
> > > promises by dynamically creating/resizing/removing queues at the right
> > > time. This allows us
> > > > to leverage the existing schedulers for the actual container
> assignment
> > > and tracking. The key benefit is to expose to the scheduler flexibility
> > of
> > > allocation, while
> > > > guaranteeing users predictable resource allocation.
> > > >
> > > > Status
> > > >
> > > > * The work has been "broken down" into 14 subtasks (+3
> patches
> > > already committed to trunk for move/kill of apps). All the issues have
> > been
> > > resolved.
> > > >
> > > > * Jenkins +1 the patch (with the exception of one test
> failure
> > > which we did not introduce, which is tracked here:
> > > https://issues.apache.org/jira/browse/MAPREDUCE-6094)
> > > >
> > > > * Simple integration with MapReduce:
> > > https://issues.apache.org/jira/browse/MAPREDUCE-6103
> > > >
> > > > * The broken-down patches have been reviewed and +1ed by
> Vinod
> > > Kumar Vavilapali, Jian He, Wangda Tan, Karthik Kambatla, and Chris
> > Douglas.
> > > Thanks to all of you for the thorough reviews!
> > > >
> > > > * The current version has been rather thoroughly tested by
> > > running it on our 250 machines research cluster for months (first
> > prototype
> > > was operational about a year ago) by:
> > > >
> > > > o   Running hundreds of thousands of job generate by a modified
> version
> > > of gridmix that exercise the reservations mechanism side-by-side normal
> > > queues.
> > > >
> > > > o   To support our integration with the resource estimation framework
> > > Perforator (http://research.microsoft.com/pubs/178971/perforator.pdf).
> > > Kaushik and Dharmesh have been pounding the reservation system for
> their
> > > research for 3-4 months now, and helped us spot few bugs and iron them
> > out.
> > > >
> > > > o   Code has been inspected/extended by 4-5 other researchers which
> are
> > > exploring integration with other systems and extensions of our
> algorithms
> > > for "reservation placement".
> > > >
> > > > * We have few ideas for follow-up extensions/improvements are
> > > tracked by the umbrella JIRA
> > > https://issues.apache.org/jira/browse/YARN-2572
> > > >
> > > > Documents and Deliverables
> > > >
> > > > * This work was accepted for publication to SoCC 2014
> > > (pre-camera ready version of the paper here):
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12671498/socc14-paper15.pdf
> > > >
> > > > * Shorter design doc:
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12628330/YARN-1051-design.pdf
> > > >
> > > > * Overall patch:
> > >
> >
> https://issues.apache.org/jira/secure/attachment/12671361/YARN-1051.1.patch
> > > >
> > > > * Per Karthik request we are preparing a small how-to
> document
> > > and example code/configuration tracked by
> > > https://issues.apache.org/jira/browse/YARN-2609
> > > >
> > > >
> > > > Credits
> > > > Myself and Subru did lots of the coding (hence the flow of patches
> from
> > > us), but this is a group effort that could have not been possible
> without
> > > the ideas and hard work of many other
> > > > folks in our research group (Microsoft-CISL). Major kudos to:  Chris
> > > Douglas, Sriram Rao, Raghu Ramakrishnan, and our intern Djellel

Failed: YARN-2617 PreCommit Build #5205

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5205/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3578 lines...]
{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerResync
  
org.apache.hadoop.yarn.server.nodemanager.containermanager.TestContainerManager
  org.apache.hadoop.yarn.server.nodemanager.TestEventFlow
  
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.TestContainersMonitor
  
org.apache.hadoop.yarn.server.nodemanager.TestNodeManagerReboot

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5205//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5205//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5205//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
749eb1a7a1cbccd8c6ca1af75d1836af8100c968 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 16 artifacts
Archive block size is 32768
Received 0 blocks and 7747657 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1879 PreCommit Build #5206

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1879
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5206/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 94 lines...]


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672394/YARN-1879.17.patch
  against trunk revision 875aa79.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5206//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
e8c82680a439b905972ff2220058f4d8147115e6 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 3140125 bytes
Compression is 0.0%
Took 2.8 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2630 PreCommit Build #5204

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2630
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5204/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3641 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672374/YARN-2630.4.patch
  against trunk revision 1f5b42a.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5204//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5204//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5204//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
43950186ce91ee24dcf2547b742c52004979e9ac logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 31 artifacts
Archive block size is 32768
Received 0 blocks and 8137269 bytes
Compression is 0.0%
Took 2.7 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1414 PreCommit Build #5211

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1414
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5211/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 28 lines...]


HEAD is now at dd1b8f2 HDFS-7176. The namenode usage message doesn't include 
"-rollingupgrade started" (cmccabe)
Previous HEAD position was dd1b8f2... HDFS-7176. The namenode usage message 
doesn't include "-rollingupgrade started" (cmccabe)
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 133 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to dd1b8f2ed8a86871517c730a9f370aca4b763514.
YARN-1414 patch is being downloaded at Wed Oct  1 22:10:59 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12632578/YARN-1221-v2.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12632578/YARN-1221-v2.patch
  against trunk revision dd1b8f2.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5211//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
27794a537f2e4fe15753ac6ea274f478ee389c0e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 41 artifacts
Archive block size is 32768
Received 0 blocks and 8362146 bytes
Compression is 0.0%
Took 3.4 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-913 PreCommit Build #5208

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-913
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5208/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3569 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672406/YARN-913-016.patch
  against trunk revision 875aa79.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 36 new 
or modified test files.

  {color:red}-1 javac{color}.  The applied patch generated 1266 javac 
compiler warnings (more than the trunk's current 1265 warnings).

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests:

  
org.apache.hadoop.yarn.applications.distributedshell.TestDistributedShell

  The test build failed in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests 

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5208//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5208//artifact/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5208//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-registry.html
Javac warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5208//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5208//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a9cd935d21acb3bf1b4a9bfbb2fb81a790e23472 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2637) maximum-am-resource-percent will be violated when resource of AM is > minimumAllocation

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2637:


 Summary: maximum-am-resource-percent will be violated when 
resource of AM is > minimumAllocation
 Key: YARN-2637
 URL: https://issues.apache.org/jira/browse/YARN-2637
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.6.0
Reporter: Wangda Tan
Priority: Critical


Currently, number of AM in leaf queue will be calculated in following way:
{code}
max_am_resource = queue_max_capacity * maximum_am_resource_percent
#max_am_number = max_am_resource / minimum_allocation
#max_am_number_for_each_user = #max_am_number * userlimit * userlimit_factor
{code}
And when submit new application to RM, it will check if an app can be activated 
in following way:
{code}
for (Iterator i=pendingApplications.iterator(); 
 i.hasNext(); ) {
  FiCaSchedulerApp application = i.next();
  
  // Check queue limit
  if (getNumActiveApplications() >= getMaximumActiveApplications()) {
break;
  }
  
  // Check user limit
  User user = getUser(application.getUser());
  if (user.getActiveApplications() < getMaximumActiveApplicationsPerUser()) 
{
user.activateApplication();
activeApplications.add(application);
i.remove();
LOG.info("Application " + application.getApplicationId() +
" from user: " + application.getUser() + 
" activated in queue: " + getQueueName());
  }
}
{code}

An example is,
If a queue has capacity = 1G, max_am_resource_percent  = 0.2, the maximum 
resource that AM can use is 200M, assuming minimum_allocation=1M, #am can be 
launched is 200, and if user uses 5M for each AM (> minimum_allocation). All 
apps can still be activated, and it will occupy all resource of a queue instead 
of only a max_am_resource_percent of a queue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2254 PreCommit Build #5209

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2254
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5209/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3187 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672416/YARN-2254.004.patch
  against trunk revision 875aa79.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5209//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5209//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5209//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
2e2d432151cc039c76f9e3911256601fcfcb11ff logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 16 artifacts
Archive block size is 32768
Received 0 blocks and 7771409 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Resolved] (YARN-1715) Per queue view in RM is not implemented correctly

[Siqi Li (JIRA)]

 [ 
https://issues.apache.org/jira/browse/YARN-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siqi Li resolved YARN-1715.
---
Resolution: Duplicate

> Per queue view in RM is not implemented correctly
> -
>
> Key: YARN-1715
> URL: https://issues.apache.org/jira/browse/YARN-1715
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Siqi Li
>Assignee: Siqi Li
>
> For now, per queue view in YARN RM has not yet implemented.
> in RmController.java it only set page title for per queue page



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-1391 PreCommit Build #5216

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1391
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5216/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 28 lines...]


HEAD is now at 52bbe0f YARN-2630. Prevented previous AM container status from 
being acquired by the current restarted AM. Contributed by Jian He.
Previous HEAD position was 52bbe0f... YARN-2630. Prevented previous AM 
container status from being acquired by the current restarted AM. Contributed 
by Jian He.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 501 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 52bbe0f11bc8e97df78a1ab9b63f4eff65fd7a76.
YARN-1391 patch is being downloaded at Wed Oct  1 22:43:11 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12618147/YARN-1391.v1.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12618147/YARN-1391.v1.patch
  against trunk revision 52bbe0f.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5216//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
d5a91776b1a036de7dc4f91d5dd681f72a221b37 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 3443562 bytes
Compression is 0.0%
Took 2.9 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2312 PreCommit Build #5207

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2312
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5207/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3858 lines...]
  against trunk revision 875aa79.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 16 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  org.apache.hadoop.mapred.TestMiniMRBringup
  org.apache.hadoop.mapred.TestClusterMapReduceTestCase
  org.apache.hadoop.mapred.TestMRIntermediateDataEncryption
  org.apache.hadoop.mapred.pipes.TestPipeApplication

  The test build failed in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client 

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5207//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5207//artifact/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5207//artifact/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5207//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
ae06c0b1ad6e7d6b0ca59c2d7ddd5ffbce268f8b logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1879 PreCommit Build #5210

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1879
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5210/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3378 lines...]
  against trunk revision 875aa79.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5210//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5210//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5210//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
c9afaca2a38d20800de19491e3e54cde837b22a3 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 57 artifacts
Archive block size is 32768
Received 0 blocks and 9398982 bytes
Compression is 0.0%
Took 2.7 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2617 PreCommit Build #5212

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5212/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2939 lines...]

/bin/kill -9 15909 
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672391/YARN-2617.5.patch
  against trunk revision dd1b8f2.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:red}-1 eclipse:eclipse{color}.  The patch failed to build with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5212//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5212//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
6e5f1e884f7c8ead5ab1f7d49cefffe4e3723d23 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1198 PreCommit Build #5217

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1198
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5217/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 22 lines...]

==
==
Testing patch for YARN-1198.
==
==


HEAD is now at 52bbe0f YARN-2630. Prevented previous AM container status from 
being acquired by the current restarted AM. Contributed by Jian He.
Previous HEAD position was 52bbe0f... YARN-2630. Prevented previous AM 
container status from being acquired by the current restarted AM. Contributed 
by Jian He.
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 52bbe0f11bc8e97df78a1ab9b63f4eff65fd7a76.
YARN-1198 patch is being downloaded at Wed Oct  1 22:51:29 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12672445/YARN-1198.9.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672445/YARN-1198.9.patch
  against trunk revision 52bbe0f.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5217//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
68fff20380770b8fda77e720c82ab743011a0dcb logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1714 PreCommit Build #5215

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1714
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5215/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 95 lines...]


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12628368/YARN-1714.v3.patch
  against trunk revision 52bbe0f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5215//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
13ce40de6ffaaf6da19862082b78eb73cbdd0151 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 3142189 bytes
Compression is 0.0%
Took 2.4 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-90 PreCommit Build #5213

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-90
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5213/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3227 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12672436/apache-yarn-90.8.patch
  against trunk revision dd1b8f2.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 6 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5213//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5213//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5213//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
a6f084b766b88911b4951597a55f31ef40c33a3e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 16 artifacts
Archive block size is 32768
Received 0 blocks and 7716995 bytes
Compression is 0.0%
Took 2.9 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1198 PreCommit Build #5219

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1198
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5219/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 40 lines...]
http://issues.apache.org/jira/secure/attachment/12672450/YARN-1198.10.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory
The patch does not appear to apply with p0 to p2
PATCH APPLICATION FAILED




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672450/YARN-1198.10.patch
  against trunk revision 8dfe54f.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5219//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
0ff8d23e40d0c0deab50bfc5c6ca02458f79990e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
ERROR: Failed to archive 
{patchprocess/patchJavacWarnings.txt=patchprocess/patchJavacWarnings.txt, 
patchprocess/trunkJavacWarnings.txt=patchprocess/trunkJavacWarnings.txt, 
patchprocess/trunkJavadocWarnings.txt=patchprocess/trunkJavadocWarnings.txt} 
due to internal error; falling back to full archiving
java.lang.IllegalStateException: checksum mismatch after transfer 
(6581801202181819975 vs. 2072449902); 
/x1/jenkins/jenkins-home/jobs/PreCommit-YARN-Build/builds/2014-10-01_23-11-07/archive/patchprocess/patchJavacWarnings.txt
 may be corrupted
at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:45)
at 
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:134)
at 
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:67)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
at hudson.model.Run.execute(Run.java:1701)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2617 PreCommit Build #5218

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5218/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2933 lines...]

/bin/kill -9 30514 
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672391/YARN-2617.5.patch
  against trunk revision 52bbe0f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:red}-1 eclipse:eclipse{color}.  The patch failed to build with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in .

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5218//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5218//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
14e53430f644fec202afcb096d5937a4f76c71a1 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2628 PreCommit Build #5214

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2628
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5214/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3188 lines...]
{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12672437/apache-yarn-2628.1.patch
  against trunk revision 52bbe0f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:red}-1 release audit{color}.  The applied patch generated 1 
release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5214//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5214//artifact/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5214//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
c842e4143aa88bfe3fe77b62548cef1516e1f071 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 16 artifacts
Archive block size is 32768
Received 0 blocks and 7771436 bytes
Compression is 0.0%
Took 2.5 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-1391 PreCommit Build #5220

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-1391
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5220/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3230 lines...]
  http://issues.apache.org/jira/secure/attachment/12672452/YARN-1391.v2.patch
  against trunk revision 8dfe54f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestDirectoryCollection

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5220//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5220//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
06f0bce89522d5aba81b759d44b8ae413ca88239 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 7716257 bytes
Compression is 0.0%
Took 3 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2624 PreCommit Build #5221

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2624
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5221/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 81 lines...]
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/ResourceLocalizationService.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/recovery/NMLeveldbStateStoreService.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/recovery/NMStateStoreService.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/localizer/TestResourceLocalizationService.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/recovery/TestNMLeveldbStateStoreService.java


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/patchJavacWarnings.txt
 2>&1
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/dev-support/test-patch.sh:
 line 469:  3559 Killed  $MVN clean test -DskipTests 
-D${PROJECT_NAME}PatchProcess $NATIVE_PROFILE -Ptest-patch > 
$PATCH_DIR/patchJavacWarnings.txt 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672456/YARN-2624.001.patch
  against trunk revision 8dfe54f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5221//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
57ec4b4d97ea7d2f967d3dbb77660404eb82bc36 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2638) Let TestRM run with all types of schedulers (FIFO, Capacity, Fair)

[Wei Yan (JIRA)]

Wei Yan created YARN-2638:
-

 Summary: Let TestRM run with all types of schedulers (FIFO, 
Capacity, Fair)
 Key: YARN-2638
 URL: https://issues.apache.org/jira/browse/YARN-2638
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Wei Yan
Assignee: Wei Yan






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2617 PreCommit Build #5222

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5222/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3230 lines...]
  http://issues.apache.org/jira/secure/attachment/12672458/YARN-2617.5.patch
  against trunk revision 0708827.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestDirectoryCollection

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5222//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5222//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
2478c71e779f5ea2fd03efcadbec69daebc63c75 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8569425 bytes
Compression is 0.0%
Took 3.2 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2635 PreCommit Build #5223

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2635
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5223/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3234 lines...]
  http://issues.apache.org/jira/secure/attachment/12672460/YARN-2635-1.patch
  against trunk revision 0708827.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestDirectoryCollection

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5223//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5223//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
2c9d8cad80560acd9b439127b4a6b327f62c0afd logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 7153537 bytes
Compression is 0.0%
Took 2.8 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2617 PreCommit Build #5225

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5225/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 37 lines...]


==
==
 Pre-build trunk to verify trunk stability and javac warnings
==
==


Compiling /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/trunkJavacWarnings.txt
 2>&1
/home/jenkins/tools/maven/latest/bin/mvn clean test javadoc:javadoc -DskipTests 
-Pdocs -DHadoopPatchProcess > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/trunkJavadocWarnings.txt
 2>&1
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/dev-support/test-patch.sh:
 line 271:  8713 Killed  $MVN clean test javadoc:javadoc 
-DskipTests -Pdocs -D${PROJECT_NAME}PatchProcess > 
$PATCH_DIR/trunkJavadocWarnings.txt 2>&1
Trunk javadoc compilation is broken?




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672458/YARN-2617.5.patch
  against trunk revision 0708827.

{color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5225//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
c0750e2fdacb8a4f0d814d1ade112a84be919cf6 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 10 artifacts
Archive block size is 32768
Received 0 blocks and 2397631 bytes
Compression is 0.0%
Took 0.55 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2624 PreCommit Build #5224

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2624
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5224/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3226 lines...]
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672461/YARN-2624.001.patch
  against trunk revision 0708827.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestDirectoryCollection

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5224//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5224//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
91285edd6206c418e9e2fb498f29122df2553c03 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (YARN-2639) TestClientToAMTokens should run with all types of schedulers

[Wei Yan (JIRA)]

Wei Yan created YARN-2639:
-

 Summary: TestClientToAMTokens should run with all types of 
schedulers
 Key: YARN-2639
 URL: https://issues.apache.org/jira/browse/YARN-2639
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Wei Yan
Assignee: Wei Yan


TestClientToAMTokens fails with FairScheduler now. We should let 
TestClientToAMTokens run with all kinds of schedulers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Failed: YARN-2617 PreCommit Build #5227

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5227/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 85 lines...]


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672468/YARN-2617.5.patch
  against trunk revision 9e40de6.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5227//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
9cb806b2d952e284637349f0a7d7b1536a6a7ca5 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 2405204 bytes
Compression is 0.0%
Took 0.66 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2639 PreCommit Build #5228

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2639
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5228/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 34 lines...]
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 9e40de6af7959ac7bb5f4e4d2833ca14ea457614.
YARN-2639 patch is being downloaded at Thu Oct  2 01:11:23 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12672470/YARN-2639-1.patch
cp: cannot stat '/home/jenkins/buildSupport/lib/*': No such file or directory


==
==
 Pre-build trunk to verify trunk stability and javac warnings
==
==


Compiling /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2
/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavacWarnings.txt
 2>&1
/home/jenkins/tools/maven/latest/bin/mvn clean test javadoc:javadoc -DskipTests 
-Pdocs -DHadoopPatchProcess > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavadocWarnings.txt
 2>&1
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/dev-support/test-patch.sh:
 line 307: 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/trunkJavadocWarnings.txt:
 No such file or directory
Trunk javadoc compilation is broken?




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672470/YARN-2639-1.patch
  against trunk revision 9e40de6.

{color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5228//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
75350465b5511f799d5fdd7162fc88f1dfb9d251 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2562 PreCommit Build #5226

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2562
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5226/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3183 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672462/YARN-2562.3.patch
  against trunk revision 0708827.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5226//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5226//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
b15e764e01c98af7922c889ac769036aa39bd1e0 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 20 artifacts
Archive block size is 32768
Received 0 blocks and 6790797 bytes
Compression is 0.0%
Took 5.1 sec
Description set: YARN-2562
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Re: Calling a merge vote for YARN-1051

[Karthik Kambatla]

+1. Nicely done, Subru and Carlo.

I have been partially involved with the work, and have reviewed some of the
patches. With some help from Subru and documentation from Carlo (thanks!),
I was able to play with the reservation system. Verified the following:
1. Reservations can be made only for the amount of resources available for
that queue.
2. Jobs submitted against a reservation run in the corresponding
"reservation" queue, and jobs submitted to the same higher-level queue but
not against a reservation run in the corresponding "default" queue.
3. The web-ui shows the reserved resources in a queue even when there are
no apps running.

There are a few follow-up items towards feature completeness, and I am okay
with working on them post merge to trunk as planned.
1. Support for FairScheduler
2. Recover reservations on RM restart/failover
3. CLI and/or REST APIs to make reservations - this is very useful for
testing
4. Documentation in the usual apt.vm format.

Cheers!
Karthik




On Wed, Oct 1, 2014 at 1:29 PM, Wangda Tan  wrote:

> +1 (non-binding),
> Reviewed several patches related to scheduler side changes. As Jian
> mentioned, this will not affect existing behavior.
> Looking forward this feature will be used by more people. Thanks for Carlo
> and Subru!
>
> Thanks,
> Wangda
>
> On Wed, Oct 1, 2014 at 1:21 PM, Jian He  wrote:
>
> > +1,
> >
> > Carlo and Subru,  great job !  thanks for your contribution !
> > I reviewed a couple of CapacityScheduler related patches, they are in
> good
> > shape. In the minimum, they are not affecting existing behavior. should
> be
> > safe to merge.
> >
> > Jian
> >
> >
> > On Wed, Oct 1, 2014 at 2:46 AM, Thomas Jungblut 
> > wrote:
> >
> > > +1 (non-binding)
> > > Thanks for adding this, really useful feature.
> > >
> > > On 30 September 2014 19:40, Chris Douglas  wrote:
> > >
> > > > +1
> > > >
> > > > Excellent work, Carlo and Subru. -C
> > > >
> > > > On Fri, Sep 26, 2014 at 11:50 AM, Carlo Curino <
> ccur...@microsoft.com>
> > > > wrote:
> > > > > (Apologies if it is delivered twice.)
> > > > >
> > > > > YARN Devs,
> > > > >
> > > > > We propose to merge YARN-1051 development branch into trunk.
> > > > >
> > > > > Key Idea:
> > > > > This work adds support for Reservations to YARN RM. The key idea is
> > to
> > > > allow users to request dedicated access to resources (a reservation),
> > > ahead
> > > > of time.
> > > > > For example I can ask for "10 containers for 1 hour sometime
> between
> > > 4pm
> > > > and 9pm today".  The RM keeps track of the accepted reservation by
> > means
> > > of
> > > > > a Plan (think it as an agenda on how the  cluster resources will be
> > > > used), and performs admission control to guarantee that if a
> > reservation
> > > is
> > > > accepted enough
> > > > > resources are set aside to satisfy it.  We enforce the reservation
> > > > promises by dynamically creating/resizing/removing queues at the
> right
> > > > time. This allows us
> > > > > to leverage the existing schedulers for the actual container
> > assignment
> > > > and tracking. The key benefit is to expose to the scheduler
> flexibility
> > > of
> > > > allocation, while
> > > > > guaranteeing users predictable resource allocation.
> > > > >
> > > > > Status
> > > > >
> > > > > * The work has been "broken down" into 14 subtasks (+3
> > patches
> > > > already committed to trunk for move/kill of apps). All the issues
> have
> > > been
> > > > resolved.
> > > > >
> > > > > * Jenkins +1 the patch (with the exception of one test
> > failure
> > > > which we did not introduce, which is tracked here:
> > > > https://issues.apache.org/jira/browse/MAPREDUCE-6094)
> > > > >
> > > > > * Simple integration with MapReduce:
> > > > https://issues.apache.org/jira/browse/MAPREDUCE-6103
> > > > >
> > > > > * The broken-down patches have been reviewed and +1ed by
> > Vinod
> > > > Kumar Vavilapali, Jian He, Wangda Tan, Karthik Kambatla, and Chris
> > > Douglas.
> > > > Thanks to all of you for the thorough reviews!
> > > > >
> > > > > * The current version has been rather thoroughly tested by
> > > > running it on our 250 machines research cluster for months (first
> > > prototype
> > > > was operational about a year ago) by:
> > > > >
> > > > > o   Running hundreds of thousands of job generate by a modified
> > version
> > > > of gridmix that exercise the reservations mechanism side-by-side
> normal
> > > > queues.
> > > > >
> > > > > o   To support our integration with the resource estimation
> framework
> > > > Perforator (http://research.microsoft.com/pubs/178971/perforator.pdf
> ).
> > > > Kaushik and Dharmesh have been pounding the reservation system for
> > their
> > > > research for 3-4 months now, and helped us spot few bugs and iron
> them
> > > out.
> > > > >
> > > > > o   Code has been inspected/extended by 4-5 other researchers which
> > are
> > > > exploring integration with other systems and extensions of our
> > algorithms
> > >

Failed: YARN-2617 PreCommit Build #5229

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2617
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5229/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3227 lines...]
  http://issues.apache.org/jira/secure/attachment/12672474/YARN-2617.6.patch
  against trunk revision 9e40de6.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

  
org.apache.hadoop.yarn.server.nodemanager.TestDirectoryCollection

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5229//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5229//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
b17a3856faece7d026b1a745a30464374e3dcc6b logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8568804 bytes
Compression is 0.0%
Took 2.7 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2638 PreCommit Build #5230

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2638
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5230/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3184 lines...]
{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672476/YARN-2638-1.patch
  against trunk revision 9e40de6.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5230//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5230//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
14441c58e75f0e93466179e9bc6e303a6c071d21 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 15 artifacts
Archive block size is 32768
Received 0 blocks and 8623892 bytes
Compression is 0.0%
Took 2.6 sec
Description set: YARN-2638
Recording test results
No test report files were found. Configuration error?
Build step 'Publish JUnit test result report' changed build result to FAILURE
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2562 PreCommit Build #5231

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2562
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5231/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 84 lines...]


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672494/YARN-2562.4.patch
  against trunk revision 9e40de6.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5231//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
dc77d717bc565310cf44edbbfef1432625dd logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 2824046 bytes
Compression is 0.0%
Took 0.71 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

Failed: YARN-2562 PreCommit Build #5232

[Apache Jenkins Server]

Jira: https://issues.apache.org/jira/browse/YARN-2562
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5232/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 84 lines...]


==
==
Determining number of patched javac warnings.
==
==


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests 
-DHadoopPatchProcess -Pnative -Ptest-patch > 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/../patchprocess/patchJavacWarnings.txt
 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12672497/YARN-2562.5.patch
  against trunk revision 9e40de6.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

{color:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5232//console

This message is automatically generated.


==
==
Adding comment to Jira.
==
==


Comment added.
36e6ab8b75aabd292cd1ce24c9587384d7f773b1 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #4749
Archived 3 artifacts
Archive block size is 32768
Received 0 blocks and 2824046 bytes
Compression is 0.0%
Took 0.71 sec
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.