Re: Request for adding to contributor's list
The JIRA is kind of funny - I couldn't add you just by your name. I can try with your JIRA alias - can you please share that? For the pre-commit builds, I believe only committers can kick them off at the moment. Please request on the JIRA, and someone following it should be able to kick it for you. On Wed, May 7, 2014 at 4:32 PM, Ashwin Shankar wrote: > Hi yarn-devs, > Can someone please add me to the yarn's > contributor's list so that I can assign JIRAs to myself in YARN project ? > > Also how do I get access to the pre-commit build machine to kick off builds > manually ? > Had trouble in the last week when couple of my pre-commit jobs was > killed/aborted and > clicking 'Submit Patch' again didn't trigger another build. > > -- > Thanks, > Ashwin >
[jira] [Created] (YARN-2070) DistributedShell publish unfriendly user information to the timeline server
Zhijie Shen created YARN-2070:
-
Summary: DistributedShell publish unfriendly user information to
the timeline server
Key: YARN-2070
URL: https://issues.apache.org/jira/browse/YARN-2070
Project: Hadoop YARN
Issue Type: Sub-task
Reporter: Zhijie Shen
Priority: Minor
Bellow is the code of using the string of current user object as the "user"
value.
{code}
entity.addPrimaryFilter("user", UserGroupInformation.getCurrentUser()
.toString());
{code}
When we use kerberos authentication, it's going to output the full name, such
as "zjshen/localhost@LOCALHOST (auth.KERBEROS)". It is not user friendly for
searching by the primary filters. It's better to use shortUserName instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Failed: YARN-1365 PreCommit Build #3746
Jira: https://issues.apache.org/jira/browse/YARN-1365
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3746/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2980 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645051/YARN-1365.001.patch
against trunk revision .
{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 1.3.9) 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-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3746//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3746//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f4ffe4fca9dd2a735be9b50d8dd708f79a4e967e 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)
##
1 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testQueueMetricsOnRMRestart
Error Message:
expected:<3> but was:<4>
Stack Trace:
java.lang.AssertionError: expected:<3> but was:<4>
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:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.assertQueueMetrics(TestRMRestart.java:1782)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testQueueMetricsOnRMRestart(TestRMRestart.java:1738)
Success: YARN-1354 PreCommit Build #3757
Jira: https://issues.apache.org/jira/browse/YARN-1354
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3757/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3011 lines...]
/bin/kill -9 1749
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645314/YARN-1354-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 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 1.3.9) 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-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3757//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3757//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a609bf6afd20663b29b15538b4f0d042eda462e4 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-1354
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-2071) Enforce more restricted permissions for the directory of Leveldb store
Zhijie Shen created YARN-2071: - Summary: Enforce more restricted permissions for the directory of Leveldb store Key: YARN-2071 URL: https://issues.apache.org/jira/browse/YARN-2071 Project: Hadoop YARN Issue Type: Sub-task Reporter: Zhijie Shen Assignee: Zhijie Shen We need to enforce more restricted permissions for the directory of Leveldb store, as w did for filesystem generic history store. -- This message was sent by Atlassian JIRA (v6.2#6252)
Success: YARN-1339 PreCommit Build #3759
Jira: https://issues.apache.org/jira/browse/YARN-1339
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3759/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3000 lines...]
/bin/kill -9 25137
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645284/YARN-1339v4.patch
against trunk revision .
{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 1.3.9) 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-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3759//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3759//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
873822e1e9efca232ea508f74faab5f70d56fdeb logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-1339
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-1474 PreCommit Build #3755
Jira: https://issues.apache.org/jira/browse/YARN-1474
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3755/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 274 lines...]
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFSLeafQueue.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairScheduler.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairSchedulerEventLog.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/TestFifoScheduler.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebApp.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/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/12644565/YARN-1474.12.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 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/3755//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2a78ac8ceafd0ee72d40c939a7ad67f7f1f437dc 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-1935 PreCommit Build #3761
Jira: https://issues.apache.org/jira/browse/YARN-1935
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3761/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4334 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645303/Timeline_Kerberos_DT_ACLs.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{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 1.3.9) 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-common-project/hadoop-common
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:
org.apache.hadoop.yarn.client.TestRMAdminCLI
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3761//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3761//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4cb407a3a609741cbbad60bdbd457f0e533ec81b 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)
##
2 tests failed.
FAILED: org.apache.hadoop.yarn.client.TestRMAdminCLI.testTransitionToActive
Error Message:
null
Stack Trace:
java.lang.UnsupportedOperationException: null
at java.util.AbstractList.remove(AbstractList.java:144)
at java.util.AbstractList$Itr.remove(AbstractList.java:360)
at java.util.AbstractCollection.remove(AbstractCollection.java:252)
at
org.apache.hadoop.ha.HAAdmin.isOtherTargetNodeActive(HAAdmin.java:173)
at org.apache.hadoop.ha.HAAdmin.transitionToActive(HAAdmin.java:144)
at org.apache.hadoop.ha.HAAdmin.runCmd(HAAdmin.java:447)
at org.apache.hadoop.ha.HAAdmin.run(HAAdmin.java:380)
at org.apache.hadoop.yarn.client.cli.RMAdminCLI.run(RMAdminCLI.java:318)
at
org.apache.hadoop.yarn.client.TestRMAdminCLI.testTransitionToActive(TestRMAdminCLI.java:180)
FAILED: org.apache.hadoop.yarn.client.TestRMAdminCLI.testHelp
Error Message:
null
Stack Trace:
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.yarn.client.TestRMAdminCLI.testError(TestRMAdminCLI.java:366)
at
org.apache.hadoop.yarn.client.TestRMAdminCLI.testHelp(TestRMAdminCLI.java:307)
[jira] [Created] (YARN-2066) Wrong field is referenced in GetApplicationsRequestPBImpl#mergeLocalToBuilder()
Ted Yu created YARN-2066:
Summary: Wrong field is referenced in
GetApplicationsRequestPBImpl#mergeLocalToBuilder()
Key: YARN-2066
URL: https://issues.apache.org/jira/browse/YARN-2066
Project: Hadoop YARN
Issue Type: Bug
Reporter: Ted Yu
Priority: Minor
{code}
if (this.finish != null) {
builder.setFinishBegin(start.getMinimumLong());
builder.setFinishEnd(start.getMaximumLong());
}
{code}
this.finish should be referenced in the if block.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Success: YARN-1338 PreCommit Build #3753
Jira: https://issues.apache.org/jira/browse/YARN-1338
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3753/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3074 lines...]
/bin/kill -9 3511
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645279/YARN-1338v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 15 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 1.3.9) 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-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3753//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3753//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
f385025f9d985dddb1da37e7027b35ae28569274 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-1338
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-2033) Investigate merging generic-history into the Timeline Store
Vinod Kumar Vavilapalli created YARN-2033: - Summary: Investigate merging generic-history into the Timeline Store Key: YARN-2033 URL: https://issues.apache.org/jira/browse/YARN-2033 Project: Hadoop YARN Issue Type: Sub-task Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Having two different stores isn't amicable to generic insights on what's happening with applications. This is to investigate porting generic-history into the Timeline Store. One goal is to try and retain most of the client side interfaces as close to what we have today. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-2065) AM cannot create new containers after restart-NM token from previous attempt used
Steve Loughran created YARN-2065:
Summary: AM cannot create new containers after restart-NM token
from previous attempt used
Key: YARN-2065
URL: https://issues.apache.org/jira/browse/YARN-2065
Project: Hadoop YARN
Issue Type: Bug
Affects Versions: 2.4.0
Reporter: Steve Loughran
Slider AM Restart failing (SLIDER-34). The AM comes back up, but it cannot
create new containers.
The Slider minicluster test {{TestKilledAM}} can replicate this reliably -it
kills the AM, then kills a container while the AM is down, which triggers a
reallocation of a container, leading to this failure.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Re: Host-specific ContainerRequest ignored
Hi Chris,
Did you make sure to pass in the ContainerRequest rack param as null?
-Sandy
On Wed, May 7, 2014 at 12:44 PM, Chris Riccomini wrote:
> Hey Guys,
>
> I am creating a container request:
>
>
> protected def requestContainers(memMb: Int, cpuCores: Int, containers:
> Int) {
>
> info("Requesting %d container(s) with %dmb of memory" format
> (containers, memMb))
>
> val capability = Records.newRecord(classOf[Resource])
>
> val priority = Records.newRecord(classOf[Priority])
>
> priority.setPriority(0)
>
> capability.setMemory(memMb)
>
> capability.setVirtualCores(cpuCores)
>
> (0 until containers).foreach(idx => amClient.addContainerRequest(new
> ContainerRequest(capability, null, null, priority)))
>
> }
>
> This pretty closely mirrors the distributed shell example.
>
> If I put an array with a host string in the ContainerRequest, YARN seems
> to completely ignore this request, and continues to put all containers on
> one or two nodes in the grid, which aren't the ones I requested, even
> though the grid is completely empty, and there are 15 nodes available. This
> also holds true if I put "false" for relax locality. I'm running the
> CapacityScheduler with a node-locality-delay set to 40. Previously, I tried
> the FifoScheduler, and it exhibited the same behavior.
>
> All NMs are just using the /default-rack for their rack. The strings that
> I'm putting in the hosts String[] parameter in ContainerRequest are hard
> coded to exactly match the NodeIds being listed in the NMs.
>
> What am I doing wrong? I feel like I'm missing some configuration on the
> capacity scheduler or NMs or something.
>
> Cheers,
> Chris
>
Failed: YARN-2049 PreCommit Build #3760
Jira: https://issues.apache.org/jira/browse/YARN-2049
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3760/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 84 lines...]
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/security/TimelineAuthenticationFilter.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/security/TimelineDelegationTokenSecretManagerService.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/security/TimelineKerberosAuthenticationHandler.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/webapp/AHSWebApp.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/TestApplicationHistoryClientService.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-applicationhistoryservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/TestApplicationHistoryServer.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/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/12645260/YARN-2049.2.patch
against trunk revision .
{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/3760//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
8b486ab4b9faf86b68715f3cbfaff6ab9f45e39f 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-1550 PreCommit Build #3756
Jira: https://issues.apache.org/jira/browse/YARN-1550
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3756/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2963 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645277/YARN-1550.001.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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/3756//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3756//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
a5ab979f33fc48a015b838d249940a4ed886637e 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)
##
All tests passed
Success: YARN-2066 PreCommit Build #3754
Jira: https://issues.apache.org/jira/browse/YARN-2066
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3754/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2971 lines...]
/bin/kill -9 10191
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645233/YARN-2066.patch
against trunk revision .
{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 1.3.9) 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-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3754//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3754//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
1d0297d99a267204550e94ac2e9c1903c520737c logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-2066
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #3753
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-1936 PreCommit Build #3758
Jira: https://issues.apache.org/jira/browse/YARN-1936
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3758/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 71 lines...]
Going to apply patch with: /usr/bin/patch -p0
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/TimelineClient.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/TimelineClientImpl.java
patching file
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/YarnClientImpl.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/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/12645288/YARN-1936.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/3758//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
5f3c6a2c8e279782c1e35eab994a1d1ebbd19f26 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-2017 PreCommit Build #3748
Jira: https://issues.apache.org/jira/browse/YARN-2017
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3748/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3216 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645077/YARN-2017.4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1277 javac
compiler warnings (more than the trunk's current 1276 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 2 new
Findbugs (version 1.3.9) 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-tools/hadoop-sls
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3748//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/3748//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/3748//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3748//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
d126e2c206f7d8273502bb3f29b3a669a76e5a11 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)
##
7 tests failed.
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testExpireKill
Error Message:
Wanted but not invoked:
eventHandler.handle(
);
-> at
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testExpireKill(TestProportionalCapacityPreemptionPolicy.java:209)
Actually, there were zero interactions with this mock.
Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked:
Wanted but not invoked:
eventHandler.handle(
);
-> at
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testExpireKill(TestProportionalCapacityPreemptionPolicy.java:209)
Actually, there were zero interactions with this mock.
at
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testExpireKill(TestProportionalCapacityPreemptionPolicy.java:209)
FAILED:
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testPreemptCycle
Error Message:
Wanted but not invoked:
eventHandler.handle(
);
-> at
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testPreemptCycle(TestProportionalCapacityPreemptionPolicy.java:186)
Actually, there were zero interactions with this mock.
Stack Trace:
org.mockito.exceptions.verification.WantedButNotInvoked:
Wanted but not invoked:
eventHandler.handle(
);
-> at
org.apache.hadoop.yarn.server.resourcemanager.monitor.capacity.TestProportionalCapacityPreemptionPolicy.testPreemptCycle(TestProportionalCapacityPreemptionPolicy.java:186)
Actually, there were zero interactions with this moc
Re: Meetup before/during Summit?
Hi Karthik, +1, it's great suggestion! Thanks, Tsuyoshi On Wed, May 14, 2014 at 7:13 PM, Karthik Kambatla wrote: > Hi folks, > > Just wanted to check if we are planning on a meetup around Summit like last > year. If we are, it would be nice to allow even those who could not > register to Summit. > > It would be great to discuss the following on-going items, among others: > >1. History and timeline servers >2. Long-running services >3. Updates on work-preserving RM/NM/AM restart >4. Update on rolling upgrade >5. Admission Control work >6. Updates on recently shipped items like RM HA > > Thanks > Karthik -- - Tsuyoshi
Success: YARN-2053 PreCommit Build #3751
Jira: https://issues.apache.org/jira/browse/YARN-2053
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3751/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2967 lines...]
/bin/kill -9 28896
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645047/YARN-2053.patch
against trunk revision .
{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 1.3.9) 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/3751//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3751//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
6532da119d9818a57090529c52259870b4a9dd49 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-2053
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Created] (YARN-2068) FairScheduler uses the same ResourceCalculator for all policies
Karthik Kambatla created YARN-2068: -- Summary: FairScheduler uses the same ResourceCalculator for all policies Key: YARN-2068 URL: https://issues.apache.org/jira/browse/YARN-2068 Project: Hadoop YARN Issue Type: Bug Components: scheduler Affects Versions: 2.4.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla FairScheduler uses the same ResourceCalculator for all policies including DRF. Need to fix that. -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: YARN-2013 PreCommit Build #3714
Jira: https://issues.apache.org/jira/browse/YARN-2013
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3714/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2988 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12643871/YARN-2013.2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3714//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3714//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
4571fbd0e1e371ac1dce9720ada1c065c125a262 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)
##
All tests passed
Re: Host-specific ContainerRequest ignored
Hey Sandy,
I *believe* so, but I might have been on the FIFO scheduler when I did (or
using Capacity with a -1 node locality delay rather than 40).
In either case, I've backed off this pursuit. We really just want even
distribution of containers on NMs, which Fair Share is providing for us
out of the box, as you've suggested already. We were initially pursuing
baking this behavior into the AM, but backed off when we had difficulties
with the host assignment (as documented on YARN-2027). Eventually, we'll
probably adopt whatever anti-affinity based features YARN ends up
providing anyway--I saw Steve open up some JIRAs on this already.
Cheers,
Chris
On 5/15/14 12:21 AM, "Sandy Ryza" wrote:
>Hi Chris,
>
>Did you make sure to pass in the ContainerRequest rack param as null?
>
>-Sandy
>
>
>On Wed, May 7, 2014 at 12:44 PM, Chris Riccomini
>wrote:
>
>> Hey Guys,
>>
>> I am creating a container request:
>>
>>
>> protected def requestContainers(memMb: Int, cpuCores: Int, containers:
>> Int) {
>>
>> info("Requesting %d container(s) with %dmb of memory" format
>> (containers, memMb))
>>
>> val capability = Records.newRecord(classOf[Resource])
>>
>> val priority = Records.newRecord(classOf[Priority])
>>
>> priority.setPriority(0)
>>
>> capability.setMemory(memMb)
>>
>> capability.setVirtualCores(cpuCores)
>>
>> (0 until containers).foreach(idx => amClient.addContainerRequest(new
>> ContainerRequest(capability, null, null, priority)))
>>
>> }
>>
>> This pretty closely mirrors the distributed shell example.
>>
>> If I put an array with a host string in the ContainerRequest, YARN seems
>> to completely ignore this request, and continues to put all containers
>>on
>> one or two nodes in the grid, which aren't the ones I requested, even
>> though the grid is completely empty, and there are 15 nodes available.
>>This
>> also holds true if I put "false" for relax locality. I'm running the
>> CapacityScheduler with a node-locality-delay set to 40. Previously, I
>>tried
>> the FifoScheduler, and it exhibited the same behavior.
>>
>> All NMs are just using the /default-rack for their rack. The strings
>>that
>> I'm putting in the hosts String[] parameter in ContainerRequest are hard
>> coded to exactly match the NodeIds being listed in the NMs.
>>
>> What am I doing wrong? I feel like I'm missing some configuration on the
>> capacity scheduler or NMs or something.
>>
>> Cheers,
>> Chris
>>
[jira] [Created] (YARN-2069) Add cross-user preemption within CapacityScheduler's leaf-queue
Vinod Kumar Vavilapalli created YARN-2069: - Summary: Add cross-user preemption within CapacityScheduler's leaf-queue Key: YARN-2069 URL: https://issues.apache.org/jira/browse/YARN-2069 Project: Hadoop YARN Issue Type: Sub-task Components: capacityscheduler Reporter: Vinod Kumar Vavilapalli Assignee: Vinod Kumar Vavilapalli Preemption today only works across queues and moves around resources across queues per demand and usage. We should also have user-level preemption within a queue, to balance capacity across users in a predictable manner. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (YARN-2067) FairScheduler update/continuous-scheduling threads should start only when after the scheduler is started
Karthik Kambatla created YARN-2067: -- Summary: FairScheduler update/continuous-scheduling threads should start only when after the scheduler is started Key: YARN-2067 URL: https://issues.apache.org/jira/browse/YARN-2067 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.4.0 Reporter: Karthik Kambatla Assignee: Karthik Kambatla Priority: Critical -- This message was sent by Atlassian JIRA (v6.2#6252)
Failed: YARN-322 PreCommit Build #3713
Jira: https://issues.apache.org/jira/browse/YARN-322
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3713/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3257 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12643831/YARN-322.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 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 1.3.9) 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
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3713//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3713//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
2f711e2430de8d99804efc216c1f769af943bd5a 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)
##
1 tests failed.
REGRESSION:
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testQueueMetricsOnRMRestart
Error Message:
expected:<3> but was:<4>
Stack Trace:
java.lang.AssertionError: expected:<3> but was:<4>
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:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.assertQueueMetrics(TestRMRestart.java:1731)
at
org.apache.hadoop.yarn.server.resourcemanager.TestRMRestart.testQueueMetricsOnRMRestart(TestRMRestart.java:1687)
Success: YARN-1474 PreCommit Build #3721
Jira: https://issues.apache.org/jira/browse/YARN-1474
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3721/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3236 lines...]
/bin/kill -9 24859
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12643953/YARN-1474.11.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 10 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 1.3.9) 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app
hadoop-tools/hadoop-sls
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/3721//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3721//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
baf982b9566fa478c70b66d1c4c608e1398e7dd5 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-1474
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-2054 PreCommit Build #3747
Jira: https://issues.apache.org/jira/browse/YARN-2054
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3747/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2974 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644753/yarn-2054-1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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/3747//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3747//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
554b8cc89680699527aacce4107f568187bbc2d6 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)
##
All tests passed
Success: YARN-1937 PreCommit Build #3750
Jira: https://issues.apache.org/jira/browse/YARN-1937
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3750/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2900 lines...]
/bin/kill -9 1497
kill: No such process
NOP
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645079/YARN-1937.3.patch
against trunk revision .
{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 1.3.9) 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-server/hadoop-yarn-server-applicationhistoryservice.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3750//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3750//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
c051168a1a45bc676b69f601ee90bb0e54893a33 logged out
==
==
Finished build.
==
==
Archiving artifacts
Description set: YARN-1937
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #3749
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
Failed: YARN-2013 PreCommit Build #3715
Jira: https://issues.apache.org/jira/browse/YARN-2013
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3715/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2991 lines...]
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12643879/YARN-2013.3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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-nodemanager.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3715//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3715//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
92b7fe97755bd3f5b60153a633b8e43b78af1b7c 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)
##
All tests passed
Failed: YARN-2017 PreCommit Build #3749
Jira: https://issues.apache.org/jira/browse/YARN-2017
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3749/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 3211 lines...]
kill: No such process
NOP
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12645088/YARN-2017.5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 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 2 new
Findbugs (version 1.3.9) 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-tools/hadoop-sls
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/3749//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/3749//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3749//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
bf574400c55c68fe8457abba8f7006ecd3c877da 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)
##
All tests passed
Failed: YARN-2050 PreCommit Build #3752
Jira: https://issues.apache.org/jira/browse/YARN-2050
Build: https://builds.apache.org/job/PreCommit-YARN-Build/3752/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2923 lines...]
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12644778/YARN-2050-2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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 1.3.9) 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-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/3752//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/3752//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
e73486b3f423c3d8a9c0bc020bf46503ae84171c logged out
==
==
Finished build.
==
==
Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on
PreCommit-YARN-Build #3751
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
All tests passed
