Failed: YARN-611 PreCommit Build #4809

[Apache Jenkins Server]

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

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




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

{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: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-api 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart
  
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairScheduler

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

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

This message is automatically generated.


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


Comment added.
daeea3a8afc28ab0f9a6a5f55d85481a809f1073 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-2492) [Umbrella] Allow for (admin) labels on nodes and resource-requests

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2492:


 Summary: [Umbrella] Allow for (admin) labels on nodes and 
resource-requests 
 Key: YARN-2492
 URL: https://issues.apache.org/jira/browse/YARN-2492
 Project: Hadoop YARN
  Issue Type: Task
  Components: api, client, resourcemanager
Reporter: Wangda Tan


Since YARN-796 is a sub JIRA of YARN-397, this JIRA is used to create and track 
sub tasks and attach split patches for YARN-796.

Let's keep all over-all discussions on YARN-796.



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

[jira] [Created] (YARN-2493) [YARN-796] API changes for users

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2493:


 Summary: [YARN-796] API changes for users
 Key: YARN-2493
 URL: https://issues.apache.org/jira/browse/YARN-2493
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: api
Reporter: Wangda Tan
Assignee: Wangda Tan


This JIRA includes API changes for users of YARN-796, like changes in 
{{ResourceRequest}}, {{ApplicationSubmissionContext}}, etc. This is a common 
part of YARN-796.



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

[jira] [Created] (YARN-2494) [YARN-796] Node label manager API and storage implementations

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2494:


 Summary: [YARN-796] Node label manager API and storage 
implementations
 Key: YARN-2494
 URL: https://issues.apache.org/jira/browse/YARN-2494
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan


This JIRA includes APIs and storage implementations of node label manager,
NodeLabelManager is an abstract class used to manage labels of nodes in the 
cluster, it has APIs to query/modify
- Nodes according to given label
- Labels according to given hostname
- Add/remove labels
- Set labels of nodes in the cluster
- Persist/recover changes of labels/labels-on-nodes to/from storage

And it has two implementations to store modifications
- Memory based storage: It will not persist changes, so all labels will be lost 
when RM restart
- FileSystem based storage: It will persist/recover to/from FileSystem (like 
HDFS), and all labels and labels-on-nodes will be recovered upon RM restart



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

[jira] [Created] (YARN-2495) [YARN-796] Allow admin specify labels in each NM (Distributed configuration)

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2495:


 Summary: [YARN-796] Allow admin specify labels in each NM 
(Distributed configuration)
 Key: YARN-2495
 URL: https://issues.apache.org/jira/browse/YARN-2495
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan


Target of this JIRA is to allow admin specify labels in each NM, this covers
- User can set labels in each NM (by setting yarn-site.xml or using script 
suggested by [~aw])
- NM will send labels to RM via ResourceTracker API
- RM will set labels in NodeLabelManager when NM register/update labels



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

[jira] [Created] (YARN-2496) [YARN-796] Changes for capacity scheduler to support allocate resource respect labels

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2496:


 Summary: [YARN-796] Changes for capacity scheduler to support 
allocate resource respect labels
 Key: YARN-2496
 URL: https://issues.apache.org/jira/browse/YARN-2496
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan


This JIRA Includes:
- Add/parse labels option to {{capacity-scheduler.xml}} similar to other 
options of queue like capacity/maximum-capacity, etc.
- Include a "default-label-expression" option in queue config, if an app 
doesn't specify label-expression, "default-label-expression" of queue will be 
used.
- Check if labels can be accessed by the queue when submit an app with 
labels-expression to queue or update ResourceRequest with label-expression
- Check labels on NM when trying to allocate ResourceRequest on the NM with 
label-expression
- Respect  labels when calculate headroom/user-limit



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

[jira] [Created] (YARN-2497) [YARN-796] Changes for fair scheduler to support allocate resource respect labels

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2497:


 Summary: [YARN-796] Changes for fair scheduler to support allocate 
resource respect labels
 Key: YARN-2497
 URL: https://issues.apache.org/jira/browse/YARN-2497
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan






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

[jira] [Created] (YARN-2500) [YARN-796] Miscellaneous changes in ResourceManager to support labels

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2500:


 Summary: [YARN-796] Miscellaneous changes in ResourceManager to 
support labels
 Key: YARN-2500
 URL: https://issues.apache.org/jira/browse/YARN-2500
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan






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

[jira] [Created] (YARN-2499) [YARN-796] Respect labels in preemption policy of fair scheduler

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2499:


 Summary: [YARN-796] Respect labels in preemption policy of fair 
scheduler
 Key: YARN-2499
 URL: https://issues.apache.org/jira/browse/YARN-2499
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan






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

[jira] [Created] (YARN-2498) [YARN-796] Respect labels in preemption policy of capacity scheduler

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2498:


 Summary: [YARN-796] Respect labels in preemption policy of 
capacity scheduler
 Key: YARN-2498
 URL: https://issues.apache.org/jira/browse/YARN-2498
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan






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

[jira] [Created] (YARN-2501) [YARN-796] Changes in AMRMClient to support labels

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2501:


 Summary: [YARN-796] Changes in AMRMClient to support labels
 Key: YARN-2501
 URL: https://issues.apache.org/jira/browse/YARN-2501
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan


Changes in AMRMClient to support labels



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

[jira] [Created] (YARN-2502) [YARN-796] Changes in distributed shell to support specify labels

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2502:


 Summary: [YARN-796] Changes in distributed shell to support 
specify labels
 Key: YARN-2502
 URL: https://issues.apache.org/jira/browse/YARN-2502
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan






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

[jira] [Created] (YARN-2503) [YARN-796] Changes in RM Web UI to better show labels to end users

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2503:


 Summary: [YARN-796] Changes in RM Web UI to better show labels to 
end users
 Key: YARN-2503
 URL: https://issues.apache.org/jira/browse/YARN-2503
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan


Include but not limited to:
- Show labels of nodes in RM/nodes page
- Show labels of queue in RM/scheduler page
- Warn user/admin if capacity of queue cannot be guaranteed according to mis 
config of labels.



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

[jira] [Created] (YARN-2504) [YARN-796] Support get/add/remove/change labels in RM admin CLI

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2504:


 Summary: [YARN-796] Support get/add/remove/change labels in RM 
admin CLI 
 Key: YARN-2504
 URL: https://issues.apache.org/jira/browse/YARN-2504
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Wangda Tan






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

[jira] [Created] (YARN-2505) [YARN-796] Support get/add/remove/change labels in RM REST API

[Wangda Tan (JIRA)]

Wangda Tan created YARN-2505:


 Summary: [YARN-796] Support get/add/remove/change labels in RM 
REST API
 Key: YARN-2505
 URL: https://issues.apache.org/jira/browse/YARN-2505
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Wangda Tan
Assignee: Craig Welch






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

Failed: YARN-2130 PreCommit Build #4810

[Apache Jenkins Server]

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

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

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

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

{color:green}+1 tests included{color}.  The patch appears to include 18 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-client 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

  
org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart

  The following test timeouts occurred in 
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

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

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

This message is automatically generated.


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


Comment added.
758182fa86654f28b36bfbebd88ab75c70c8a499 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-2493 PreCommit Build #4811

[Apache Jenkins Server]

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

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



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

{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}.  The applied patch generated 1296 javac 
compiler warnings (more than the trunk's current 1265 warnings).

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 2 
warning messages.
See 
https://builds.apache.org/job/PreCommit-YARN-Build/4811//artifact/trunk/patchprocess/diffJavadocWarnings.txt
 for details.

{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/4811//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/4811//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4811//console

This message is automatically generated.


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


Comment added.
8ad017ba40b7a99ad5cbc506e367edd7cc7ba491 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.

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

[Apache Jenkins Server]

See 

Failed: YARN-2493 PreCommit Build #4812

[Apache Jenkins Server]

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

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




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

{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}.  The applied patch generated 1296 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: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/4812//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/4812//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4812//console

This message is automatically generated.


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


Comment added.
1a548fbc25df1f2e2aea1aab8ce0f92bfdf98ba6 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-2394 PreCommit Build #4813

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 19 lines...]
[PreCommit-YARN-Build] $ /bin/bash /tmp/hudson377264675032012409.sh
Running in Jenkins mode


==
==
Testing patch for YARN-2394.
==
==


HEAD is now at 3425ae5 HDFS-2975. Rename with overwrite flag true can make 
NameNode to stuck in safemode on NN (crash + restart). (Yi Liu via umamahesh)
Switched to branch 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
YARN-2394 patch is being downloaded at Wed Sep  3 15:21:39 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12666241/YARN-2394-6.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/12666241/YARN-2394-6.patch
  against trunk revision 3425ae5.

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

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

This message is automatically generated.


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


Comment added.
fd6870974e4ccdc912a47d3a56b6f90daa4414c8 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-2394 PreCommit Build #4814

[Apache Jenkins Server]

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

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




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12666250/YARN-2394-7.patch
  against trunk revision 3425ae5.

{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: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/4814//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4814//console

This message is automatically generated.


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


Comment added.
21aa082e79d5d9ca07fabd34623a132b2fb46840 logged out


==
==
Finished build.
==
==


Archiving artifacts
ERROR: No artifacts found that match the file pattern "../patchprocess/*". 
Configuration error?
ERROR: ?../patchprocess/*? doesn?t match anything, but ?patchprocess/*? does. 
Perhaps that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[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-2506) TimelineClient should NOT be in yarn-common project

[Vinod Kumar Vavilapalli (JIRA)]

Vinod Kumar Vavilapalli created YARN-2506:
-

 Summary: TimelineClient should NOT be in yarn-common project
 Key: YARN-2506
 URL: https://issues.apache.org/jira/browse/YARN-2506
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Vinod Kumar Vavilapalli
Assignee: Vinod Kumar Vavilapalli


YARN-2298 incorrectly moved TimelineClient to yarn-common project. It doesn't 
belong there, we should move it back to yarn-client module.



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

[jira] [Resolved] (YARN-2086) AmIpFilter to support REST APIs

[Steve Loughran (JIRA)]

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

Steve Loughran resolved YARN-2086.
--
Resolution: Won't Fix

you can't open the filter and keep the AM secure ... the only secure solution 
here is for the proxy to support the full set of HTTP verbs

> AmIpFilter to support REST APIs
> ---
>
> Key: YARN-2086
> URL: https://issues.apache.org/jira/browse/YARN-2086
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: webapp
>Reporter: Steve Loughran
>
> The {{AmIpFilter}} doesn't like REST APIs, as all operations are redirected 
> to the proxy as a 302. Even if the proxy did relay all verbs, the filter 
> would need to return a 307 and hope the client was enable to re-issue the 
> verb.
> The alternative is to have a dedicated part of the webapp to be unproxied, 
> which we did with a custom filter to not relay "/ws/*", or even allow apps to 
> register a rest endpoint directly, either in the AppReport data, or via the 
> YARN-913 registry



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

[jira] [Created] (YARN-2507) Document CORS configuration for ATS

[Jonathan Eagles (JIRA)]

Jonathan Eagles created YARN-2507:
-

 Summary: Document CORS configuration for ATS
 Key: YARN-2507
 URL: https://issues.apache.org/jira/browse/YARN-2507
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: documentation
Affects Versions: 2.6.0
Reporter: Jonathan Eagles
Assignee: Mit Desai


CORS support was added for ATS as part of YARN-2277. This jira is to document 
configuration for ATS CORS support.



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

Failed: YARN-913 PreCommit Build #4815

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 138 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/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
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/TestRMWebAppFairScheduler.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/MiniYARNCluster.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/TestMiniYARNClusterRegistry.java
patching file hadoop-yarn-project/hadoop-yarn/pom.xml


==
==
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/12666278/YARN-913-001.patch
  against trunk revision 1dcaba9.

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

{color:green}+1 tests included{color}.  The patch appears to include 24 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/4815//console

This message is automatically generated.


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


Comment added.
7dbfaa0277011214a15193b6130d0bb547dac2b7 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-2508) CORS configuration parameters prefix are not honored

[Jonathan Eagles (JIRA)]

Jonathan Eagles created YARN-2508:
-

 Summary: CORS configuration parameters prefix are not honored
 Key: YARN-2508
 URL: https://issues.apache.org/jira/browse/YARN-2508
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: timelineserver
Reporter: Jonathan Eagles


CrossOriginFilterInitializer specifies a prefix to have http server read 
parameters. However, it neither trims the prefix nor passes the prefix to the 
CrossOriginFilter.



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

[jira] [Created] (YARN-2509) Enable Cross Origin Filter for timeline server only and not all Yarn servers

[Jonathan Eagles (JIRA)]

Jonathan Eagles created YARN-2509:
-

 Summary: Enable Cross Origin Filter for timeline server only and 
not all Yarn servers
 Key: YARN-2509
 URL: https://issues.apache.org/jira/browse/YARN-2509
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Jonathan Eagles
Assignee: Mit Desai






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

[DISCUSS] Hadoop 2.5.1

[Karthik Kambatla]

Hi folks

Now that all issues with target 2.5.1 are committed, I am planning to cut
an RC for 2.5.1 this Friday. The fixes going into 2.5.1 are -
http://s.apache.org/2Mz

Are there any other "Blocker" issues that we would like to get into 2.5.1?
If there are any, please mark them as "Blocker" and target "2.5.1".

Committers - please avoid committing non-blockers to 2.5.1.

I have put together a new wiki for the release process
. Would
greatly appreciate any eyeballs I can get on improving it. The wiki
reflects our migration to git, the updated create-release script that
avoids manual massaging of tarballs and other minor improvements.

Thanks
Karthik

[jira] [Created] (YARN-2510) RM can drop container completion events

[Jason Lowe (JIRA)]

Jason Lowe created YARN-2510:


 Summary: RM can drop container completion events
 Key: YARN-2510
 URL: https://issues.apache.org/jira/browse/YARN-2510
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.5.0
Reporter: Jason Lowe
Priority: Critical


The RM can drop container completion events and fail to report them to the AM.  
Details in the first comment.



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

Failed: YARN-2046 PreCommit Build #4817

[Apache Jenkins Server]

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

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




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12666320/YARN-2046.patch
  against trunk revision 1dcaba9.

{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: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/4817//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4817//console

This message is automatically generated.


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


Comment added.
a361082dc5c9f7f0e8e4e4faac78ce605026c8a8 logged out


==
==
Finished build.
==
==


Archiving artifacts
ERROR: No artifacts found that match the file pattern "../patchprocess/*". 
Configuration error?
ERROR: ?../patchprocess/*? doesn?t match anything, but ?patchprocess/*? does. 
Perhaps that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[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-2509 PreCommit Build #4818

[Apache Jenkins Server]

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

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




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

{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 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-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/4818//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4818//console

This message is automatically generated.


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


Comment added.
e10d1108270919d16a883ac5e49c7ba1ff7c4419 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-1707 PreCommit Build #4819

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 109 lines...]
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/CapacitySchedulerInfo.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/CapacitySchedulerQueueInfo.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/capacity/TestCapacityScheduler.java
Hunk #1 succeeded at 408 (offset 8 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/TestCapacitySchedulerDynamicBehavior.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/capacity/TestReservationQueue.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/12666353/YARN-1707.7.patch
  against trunk revision d9a03e2.

{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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.


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


Comment added.
3a5da89ceb92badea836d18a16848145bb5339de 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] [Resolved] (YARN-2510) RM can drop container completion events

[Jason Lowe (JIRA)]

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

Jason Lowe resolved YARN-2510.
--
Resolution: Invalid

My apologies, this is an invalid report.  I accidentally grabbed the wrong 
container ID when searching the RM log because after looking again I don't see 
the RM seeing the container completion event.  The 9 missing completion events 
on the AM were all from the same node, so I think this is a case of a poorly 
handled node failure that lead to a MapReduce app hang.

I'll file a separate JIRA to track handling that case better.  That's probably 
is a MapReduce fix since the RM can't tell the container is no longer needed 
unless either the NM reports it completing (which it failed to do in this case 
due to a bad node) or the AM explicitly releases the container.

> RM can drop container completion events
> ---
>
> Key: YARN-2510
> URL: https://issues.apache.org/jira/browse/YARN-2510
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: resourcemanager
>Affects Versions: 2.5.0
>Reporter: Jason Lowe
>Priority: Critical
>
> The RM can drop container completion events and fail to report them to the 
> AM.  Details in the first comment.



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

Failed: YARN-1492 PreCommit Build #4816

[Apache Jenkins Server]

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

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




{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12666111/YARN-1492-all-trunk-v4.patch
  against trunk revision 1dcaba9.

{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:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common 
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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
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/4816//testReport/
Release audit warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/4816//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/4816//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-common.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4816//console

This message is automatically generated.


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


Comment added.
84007920e25e5245a043ff606becf4600edbfd39 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-1707 PreCommit Build #4820

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 105 lines...]
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/common/QueueEntitlement.java
patching file 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/webapp/dao/CapacitySchedulerQueueInfo.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/capacity/TestCapacityScheduler.java
Hunk #1 succeeded at 408 (offset 8 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/TestCapacitySchedulerDynamicBehavior.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/capacity/TestReservationQueue.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/12666416/YARN-1707.8.patch
  against trunk revision 8f1a668.

{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:red}-1 javac{color:red}.  The patch appears to cause the build to 
fail.

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

This message is automatically generated.


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


Comment added.
5f90051f408af0e68ea7bb21ac1f712cc6f730a0 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-2511) Allow All Origins by default when Cross Origin Filter is enabled

[Jonathan Eagles (JIRA)]

Jonathan Eagles created YARN-2511:
-

 Summary: Allow All Origins by default when Cross Origin Filter is 
enabled
 Key: YARN-2511
 URL: https://issues.apache.org/jira/browse/YARN-2511
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: timelineserver
Reporter: Jonathan Eagles
Assignee: Jonathan Eagles






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

Failed: YARN-2511 PreCommit Build #4822

[Apache Jenkins Server]

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

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




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12666421/YARN-2511-v1.patch
  against trunk revision 8f1a668.

{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-applicationhistoryservice.

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

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

This message is automatically generated.


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


Comment added.
2eed87a8ecba39242041883ab87673072bbbd1d7 logged out


==
==
Finished build.
==
==


Archiving artifacts
ERROR: No artifacts found that match the file pattern "../patchprocess/*". 
Configuration error?
ERROR: ?../patchprocess/*? doesn?t match anything, but ?patchprocess/*? does. 
Perhaps that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[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-611 PreCommit Build #4821

[Apache Jenkins Server]

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

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




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12666419/YARN-611.7.patch
  against trunk revision 8f1a668.

{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: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-resourcemanager.

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

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

This message is automatically generated.


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


Comment added.
f22618870e6df078af57db96dbeb626af0b823c8 logged out


==
==
Finished build.
==
==


Archiving artifacts
ERROR: No artifacts found that match the file pattern "../patchprocess/*". 
Configuration error?
ERROR: ?../patchprocess/*? doesn?t match anything, but ?patchprocess/*? does. 
Perhaps that?s what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE
[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.