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

2015-01-26 Thread Apache Jenkins Server 
See 

Changes:

[stevel] HADOOP-11419 improve hadoop-maven-plugins.  (Hervé Boutemy via stevel)

[xgong] YARN-3024. LocalizerRunner should give DIE action when all resources are

[ozawa] HADOOP-11450. Cleanup DistCpV1 not to use deprecated methods and fix 
javadocs. Contributed by Varun Saxena.

--
[...truncated 4533 lines...]
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestMaxRunningAppsEnforcer
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.13 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestMaxRunningAppsEnforcer
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerEventLog
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.271 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerEventLog
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerPreemption
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.979 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerPreemption
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.667 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestAbstractYarnScheduler
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.521 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.TestAbstractYarnScheduler
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestQueueMappings
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.029 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestQueueMappings
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestReservationQueue
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.208 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestReservationQueue
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestReservations
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.126 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestReservations
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestParentQueue
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.195 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestParentQueue
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerDynamicBehavior
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.988 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerDynamicBehavior
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerNodeLabelUpdate
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.685 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerNodeLabelUpdate
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestChildQueueOrder
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.959 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestChildQueueOrder
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler
Tests run: 30, Fail

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

2015-01-26 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/85/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 4726 lines...]
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.216 sec - in 
org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesCapacitySched

Results :

Failed tests: 
  TestFSRMStateStore.testFSRMStateStoreClientRetry:289 null

Tests run: 1005, Failures: 1, Errors: 0, Skipped: 1

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-yarn ... SUCCESS [  2.967 s]
[INFO] hadoop-yarn-api ... SUCCESS [01:02 min]
[INFO] hadoop-yarn-common  SUCCESS [02:00 min]
[INFO] hadoop-yarn-server  SUCCESS [  0.056 s]
[INFO] hadoop-yarn-server-common . SUCCESS [ 31.969 s]
[INFO] hadoop-yarn-server-nodemanager  SUCCESS [06:04 min]
[INFO] hadoop-yarn-server-web-proxy .. SUCCESS [ 13.657 s]
[INFO] hadoop-yarn-server-applicationhistoryservice .. SUCCESS [02:46 min]
[INFO] hadoop-yarn-server-resourcemanager  FAILURE [47:31 min]
[INFO] hadoop-yarn-server-tests .. SKIPPED
[INFO] hadoop-yarn-client  SKIPPED
[INFO] hadoop-yarn-server-sharedcachemanager . SKIPPED
[INFO] hadoop-yarn-applications .. SKIPPED
[INFO] hadoop-yarn-applications-distributedshell . SKIPPED
[INFO] hadoop-yarn-applications-unmanaged-am-launcher  SKIPPED
[INFO] hadoop-yarn-site .. SKIPPED
[INFO] hadoop-yarn-registry .. SKIPPED
[INFO] hadoop-yarn-project ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:00 h
[INFO] Finished at: 2015-01-26T11:32:29+00:00
[INFO] Final Memory: 72M/902M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project hadoop-yarn-server-resourcemanager: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk-Java8/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/target/surefire-reports
 for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :hadoop-yarn-server-resourcemanager
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Updating YARN-3024
Updating HADOOP-11450
Updating HADOOP-11419
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
1 tests failed.
REGRESSION:  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry

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.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry(TestFSRMStateStore.java:289)

Success: YARN-41 PreCommit Build #6416

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-41
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6416/

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




{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12694514/YARN-41-3.patch
  against trunk revision 7b82c4a.

{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 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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager
 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests.

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

This message is automatically generated.


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


Comment added.
f94eb47bec70603a50f74e6fdee646aab0e06f38 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6415
Archived 30 artifacts
Archive block size is 32768
Received 238 blocks and 1454455 bytes
Compression is 84.3%
Took 1.1 sec
Description set: YARN-41
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

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

2015-01-26 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk/819/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 9451 lines...]
  TestRMAdminCLI.testAccessLocalNodeLabelManager:403 expected:<0> but was:<-1>

Tests in error: 
  TestRMAdminCLI.testReplaceLabelsOnNode:504 » IO Node-label-based scheduling 
is...
  TestRMAdminCLI.testRemoveFromClusterNodeLabels:475 » IO Node-label-based 
sched...
  TestRMAdminCLI.testReplaceLabelsOnNodeWithPort:535 » IO Node-label-based 
sched...

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

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-yarn ... SUCCESS [  3.127 s]
[INFO] hadoop-yarn-api ... SUCCESS [02:57 min]
[INFO] hadoop-yarn-common  SUCCESS [02:40 min]
[INFO] hadoop-yarn-server  SUCCESS [  0.080 s]
[INFO] hadoop-yarn-server-common . SUCCESS [ 40.417 s]
[INFO] hadoop-yarn-server-nodemanager  SUCCESS [06:13 min]
[INFO] hadoop-yarn-server-web-proxy .. SUCCESS [ 21.685 s]
[INFO] hadoop-yarn-server-applicationhistoryservice .. SUCCESS [03:00 min]
[INFO] hadoop-yarn-server-resourcemanager  SUCCESS [48:33 min]
[INFO] hadoop-yarn-server-tests .. SUCCESS [02:14 min]
[INFO] hadoop-yarn-client  FAILURE [06:23 min]
[INFO] hadoop-yarn-server-sharedcachemanager . SKIPPED
[INFO] hadoop-yarn-applications .. SKIPPED
[INFO] hadoop-yarn-applications-distributedshell . SKIPPED
[INFO] hadoop-yarn-applications-unmanaged-am-launcher  SKIPPED
[INFO] hadoop-yarn-site .. SKIPPED
[INFO] hadoop-yarn-registry .. SKIPPED
[INFO] hadoop-yarn-project ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:13 h
[INFO] Finished at: 2015-01-26T11:45:09+00:00
[INFO] Final Memory: 81M/883M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project hadoop-yarn-client: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/target/surefire-reports
 for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :hadoop-yarn-client
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
Updating YARN-3024
Updating HADOOP-11450
Updating HADOOP-11419
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
5 tests failed.
FAILED:  
org.apache.hadoop.yarn.client.cli.TestRMAdminCLI.testReplaceLabelsOnNode

Error Message:
Node-label-based scheduling is disabled. Please check yarn.node-labels.enabled

Stack Trace:
java.io.IOException: Node-label-based scheduling is disabled. Please check 
yarn.node-labels.enabled
at 
org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager.addToCluserNodeLabels(CommonNodeLabelsManager.java:272)
at 
org.apache.hadoop.yarn.client.cli.TestRMAdminCLI.testReplaceLabelsOnNode(TestRMAdminCLI.java:504)


FAILED:  
org.apache.hadoop.yarn.client.cli.TestRMAdminCLI.testRemoveFromClusterNodeLabels

Error Message:
Node-label-based scheduling is disabled. Please check yarn.node-labels.enabled

Stack Trace:
java.io.IOException: Node-label-based scheduling is disabled. Please check 
yarn.node-labels.enabled
at 
org.apache.hadoop.yarn.nodelabels.CommonNodeLabelsManager.addToCluserNodeLabels(CommonNodeLabelsManager.java:272)
at 
org.apache.hadoop.yarn.client.cli.TestRMAdminCLI.testRemoveFromClusterNodeLabels(TestRMAdminCLI.java:475)


FAILED:  
org.apache.hadoop.yarn.client.cli.TestRMAdminCLI.testReplaceLabelsOnNodeWithPort

Error Message:
N

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

2015-01-26 Thread Apache Jenkins Server 
See 

Changes:

[stevel] HADOOP-11419 improve hadoop-maven-plugins.  (Hervé Boutemy via stevel)

[xgong] YARN-3024. LocalizerRunner should give DIE action when all resources are

[ozawa] HADOOP-11450. Cleanup DistCpV1 not to use deprecated methods and fix 
javadocs. Contributed by Varun Saxena.

--
[...truncated 9258 lines...]
---

---
 T E S T S
---
Running org.apache.hadoop.yarn.server.TestDiskFailures
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 18.809 sec - in 
org.apache.hadoop.yarn.server.TestDiskFailures
Running org.apache.hadoop.yarn.server.TestContainerManagerSecurity
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 88.326 sec - in 
org.apache.hadoop.yarn.server.TestContainerManagerSecurity
Running org.apache.hadoop.yarn.server.TestRMNMSecretKeys
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.321 sec - in 
org.apache.hadoop.yarn.server.TestRMNMSecretKeys
Running org.apache.hadoop.yarn.server.TestMiniYARNClusterForHA
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.207 sec - in 
org.apache.hadoop.yarn.server.TestMiniYARNClusterForHA

Results :

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

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

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

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

[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (dist-enforce) @ 
hadoop-yarn-server-tests ---
[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
hadoop-yarn-server-tests ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (module-javadocs) @ 
hadoop-yarn-server-tests ---
[INFO] 
Loading source files for package org.apache.hadoop.yarn.proto...
Constructing Javadoc information...
Standard Doclet version 1.7.0_55
Building tree for all the packages and classes...
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating

[jira] [Created] (YARN-3096) RM Configured Min User % still showing as 100% in Scheduler

2015-01-26 Thread Hari Sekhon (JIRA) 
Hari Sekhon created YARN-3096:
-

 Summary: RM Configured Min User % still showing as 100% in 
Scheduler
 Key: YARN-3096
 URL: https://issues.apache.org/jira/browse/YARN-3096
 Project: Hadoop YARN
  Issue Type: Bug
  Components: capacityscheduler, resourcemanager, scheduler
Affects Versions: 2.6.0
 Environment: HDP 2.2 with RM HA & Kerberos managed by Ambari 1.7
Reporter: Hari Sekhon
 Attachments: screenshot-1.png

After setting the Capacity Scheduler minimum-user-limit-percent to 25 it still 
shows as 100% in the RM web UI under Scheduler even after doing queue refresh 
and even fully restarting both HA Resource Managers.

/etc/hadoop/conf/capacity-scheduler.xml:
{code}

  yarn.scheduler.capacity.default.minimum-user-limit-percent
  25

...{code}

This cluster is Kerberized and managed by Ambari, I've refreshed via both 
Ambari and manually on the command line via
{code}yarn rmadmin -refreshQueues{code}
but it still shows the same.

Screenshot attached to show it still shows 100% instead of the expected 25%.



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

[jira] [Resolved] (YARN-3096) RM Configured Min User % still showing as 100% in Scheduler

2015-01-26 Thread Jason Lowe (JIRA) 

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

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

The user interface still shows 100% because the wrong property is being set, so 
the queue is not using a 25% user limit.  This can also be verified by 
examining the RM logs after it starts up or the queues are refreshed.

In queue properties the queue name needs to be the full path including "root", 
so the property should be 
yarn.scheduler.capacity.root.default.miminum-user-limit-percent.  See the 
[CapacityScheduler 
documentation|http://hadoop.apache.org/docs/r2.6.0/hadoop-yarn/hadoop-yarn-site/CapacityScheduler.html]
 for more details.

> RM Configured Min User % still showing as 100% in Scheduler
> ---
>
> Key: YARN-3096
> URL: https://issues.apache.org/jira/browse/YARN-3096
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: capacityscheduler, resourcemanager, scheduler
>Affects Versions: 2.6.0
> Environment: HDP 2.2 with RM HA & Kerberos managed by Ambari 1.7
>Reporter: Hari Sekhon
> Attachments: screenshot-1.png
>
>
> After setting the Capacity Scheduler minimum-user-limit-percent to 25 it 
> still shows as 100% in the RM web UI under Scheduler even after doing queue 
> refresh and even fully restarting both HA Resource Managers.
> /etc/hadoop/conf/capacity-scheduler.xml:
> {code}
> 
>   yarn.scheduler.capacity.default.minimum-user-limit-percent
>   25
> 
> ...{code}
> This cluster is Kerberized and managed by Ambari, I've refreshed via both 
> Ambari and manually on the command line via
> {code}yarn rmadmin -refreshQueues{code}
> but it still shows the same.
> Screenshot attached to show it still shows 100% instead of the expected 25%.



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

[jira] [Created] (YARN-3097) Logging of resource recovery on NM restart has redundancies

2015-01-26 Thread Jason Lowe (JIRA) 
Jason Lowe created YARN-3097:


 Summary: Logging of resource recovery on NM restart has 
redundancies
 Key: YARN-3097
 URL: https://issues.apache.org/jira/browse/YARN-3097
 Project: Hadoop YARN
  Issue Type: Bug
  Components: nodemanager
Affects Versions: 2.5.0
Reporter: Jason Lowe
Priority: Minor


ResourceLocalizationService logs that it is recovering a resource with the 
remote and local paths, but then very shortly afterwards the LocalizedResource 
emits an INIT->LOCALIZED transition that also logs the same remote and local 
paths.  The recovery message should be a debug message, since it's not 
conveying any useful information that isn't already covered by the resource 
state transition log.



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

Failed: YARN-2808 PreCommit Build #6417

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2808
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6417/

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

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

{color:green}+1 tests included{color}.  The patch appears to include 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:red}-1 findbugs{color}.  The patch appears to introduce 1 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:

  org.apache.hadoop.yarn.client.TestResourceTrackerOnHA
  org.apache.hadoop.yarn.client.api.impl.TestAMRMClient
  
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA
  org.apache.hadoop.yarn.client.cli.TestRMAdminCLI

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6417//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/6417//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6417//console

This message is automatically generated.


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


Comment added.
f0801642a0dfa6fcb577e325fbc4adc1bf2d643c logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
16 tests failed.
FAILED:  
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA.testGetContainersOnHA

Error Message:
Call From asf905.gq1.ygridcore.net/67.195.81.149 to 
asf905.gq1.ygridcore.net:28032 failed on connection exception: 
java.net.ConnectException: Connection refused; For more details see:  
http://wiki.apache.org/hadoop/ConnectionRefused

Stack Trace:
java.net.ConnectException: Call From asf905.gq1.ygridcore.net/67.195.81.149 to 
asf905.gq1.ygridcore.net:28032 failed on connection exception: 
java.net.ConnectException: Connection refused; For more details see:  
http://wiki.apache.org/hadoop/ConnectionRefused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
at 
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:530)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:494)
at 
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:607)
at 
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:705)
at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:368)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1521)
at org.apache.hadoop.ipc.Client.call(Client.java:1438)
at org.apache.hadoop.ipc.Client.call(Client.java:1399)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:230)
at com.sun.proxy.$Proxy17.getContainers(Unknown Source)
at 
org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getContainers(ApplicationClientProtocolPBClientImpl.java:410)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI

Failed: YARN-2897 PreCommit Build #6418

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2897
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6418/

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

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

{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-server/hadoop-yarn-server-applicationhistoryservice.

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

This message is automatically generated.


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


Comment added.
7fc181e7004554ad91a2fc2512579c181b4b4462 logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Created] (YARN-3098) Create common QueueCapacities class in Capacity Scheduler to track capacities-by-labels of queues

2015-01-26 Thread Wangda Tan (JIRA) 
Wangda Tan created YARN-3098:


 Summary: Create common QueueCapacities class in Capacity Scheduler 
to track capacities-by-labels of queues
 Key: YARN-3098
 URL: https://issues.apache.org/jira/browse/YARN-3098
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: capacityscheduler
Reporter: Wangda Tan
Assignee: Wangda Tan


Similar to YARN-3092, after YARN-796, now queues (ParentQueue and LeafQueue) 
need to track capacities-label (e.g. absolute-capacity, maximum-capacity, 
absolute-capacity, absolute-maximum-capacity, etc.). It's better to have a 
class to encapsulate these capacities to make both better 
maintainability/readability and fine-grained locking.



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

Re: How to edit contributor list

2015-01-26 Thread Ravi Prakash 
I too would like that capability. ~raviprak
 

 On Friday, January 23, 2015 11:27 AM, Tsuyoshi Ozawa  
wrote:
   

 Hi,

I'd like to edit contributor list to add new contributors. Does anyone
know how to do that?

- Tsuyoshi

Failed: YARN-3028 PreCommit Build #6419

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3028
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6419/

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

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

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

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
d548f4de49a8c7b6ce3251b668a76e478ee8c8e1 logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
10 tests failed.
FAILED:  
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA.testGetNewApplicationOnHA

Error Message:
Call From asf908.gq1.ygridcore.net/67.195.81.152 to 
asf908.gq1.ygridcore.net:28032 failed on connection exception: 
java.net.ConnectException: Connection refused; For more details see:  
http://wiki.apache.org/hadoop/ConnectionRefused

Stack Trace:
java.net.ConnectException: Call From asf908.gq1.ygridcore.net/67.195.81.152 to 
asf908.gq1.ygridcore.net:28032 failed on connection exception: 
java.net.ConnectException: Connection refused; For more details see:  
http://wiki.apache.org/hadoop/ConnectionRefused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
at 
org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:530)
at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:494)
at 
org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:607)
at 
org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:705)
at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:368)
at org.apache.hadoop.ipc.Client.getConnection(Client.java:1521)
at org.apache.hadoop.ipc.Client.call(Client.java:1438)
at org.apache.hadoop.ipc.Client.call(Client.java:1399)
at 
org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:230)
at com.sun.proxy.$Proxy17.getNewApplication(Unknown Source)
at 
org.apache.hadoop.yarn.api.impl.pb.client.ApplicationClientProtocolPBClientImpl.getNewApplication(ApplicationClientProtocolPBClientImpl.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

Failed: YARN-2897 PreCommit Build #6420

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2897
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6420/

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

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

{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-server/hadoop-yarn-server-applicationhistoryservice.

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

This message is automatically generated.


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


Comment added.
6cd84db7f4d9961e032d9a749a0761f45fec59f5 logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6416
Archived 15 artifacts
Archive block size is 32768
Received 227 blocks and 1199106 bytes
Compression is 86.1%
Took 0.77 sec
[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

[jira] [Created] (YARN-3099) Capacity Scheduler LeafQueue/ParentQueue should use ResourceUsage to track resources-by-label.

2015-01-26 Thread Wangda Tan (JIRA) 
Wangda Tan created YARN-3099:


 Summary: Capacity Scheduler LeafQueue/ParentQueue should use 
ResourceUsage to track resources-by-label.
 Key: YARN-3099
 URL: https://issues.apache.org/jira/browse/YARN-3099
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Wangda Tan
Assignee: Wangda Tan






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

Failed: YARN-3075 PreCommit Build #6421

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3075
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6421/

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

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

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

  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore

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

This message is automatically generated.


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


Comment added.
b7701131c2259fb0d7d925c50e91432b081d5c3d logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry

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.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry(TestFSRMStateStore.java:289)

Failed: YARN-2897 PreCommit Build #6423

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2897
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6423/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 2993 lines...]
/bin/grep: 
/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build@2/../patchprocess/patch:
 No such file or directory
cat: /tmp/tmp.modules.7737: No such file or directory
rm: cannot remove '/tmp/tmp.modules.7737': No such file or directory




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

{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:red}-1 eclipse:eclipse{color}.  The patch failed to build with 
eclipse:eclipse.

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

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

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

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

This message is automatically generated.


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


Comment added.
b2511cda4bcbe8d695f6b8c8e1a620172e10b4e8 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-3098 PreCommit Build #6422

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3098
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6422/

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

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

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

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

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

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

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

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

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

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

  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore

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

This message is automatically generated.


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


Comment added.
086c7f40fabc20932ae33b69be9e8f733462c6b6 logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry

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.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry(TestFSRMStateStore.java:289)

Success: YARN-3022 PreCommit Build #6424

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3022
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6424/

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




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

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

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
3dc7f88f5d048a9814d36ee7a1a32f11c56ec242 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6416
Archived 20 artifacts
Archive block size is 32768
Received 40 blocks and 8286396 bytes
Compression is 13.7%
Took 1.8 sec
Description set: YARN-3022
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Re: How to edit contributor list

2015-01-26 Thread Karthik Kambatla 
https://issues.apache.org/jira/plugins/servlet/project-config/YARN/roles

Ravi - you already had permissions to add contributors. Tsuyoshi - I just
added you.

On Tue, Jan 27, 2015 at 1:26 AM, Ravi Prakash  wrote:

> I too would like that capability. ~raviprak
>
>
>  On Friday, January 23, 2015 11:27 AM, Tsuyoshi Ozawa <
> oz...@apache.org> wrote:
>
>
>  Hi,
>
> I'd like to edit contributor list to add new contributors. Does anyone
> know how to do that?
>
> - Tsuyoshi
>
>
>
>



-- 
Karthik Kambatla
Software Engineer, Cloudera Inc.

http://five.sentenc.es

Success: YARN-3099 PreCommit Build #6425

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3099
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6425/

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




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

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

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

This message is automatically generated.


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


Comment added.
4adda1fd5d94d199861a316997959c64e5c1b8ea logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6424
Archived 15 artifacts
Archive block size is 32768
Received 47 blocks and 7311259 bytes
Compression is 17.4%
Took 2.7 sec
Description set: YARN-3099
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Created] (YARN-3100) Make YARN authorization pluggable

2015-01-26 Thread Jian He (JIRA) 
Jian He created YARN-3100:
-

 Summary: Make YARN authorization pluggable
 Key: YARN-3100
 URL: https://issues.apache.org/jira/browse/YARN-3100
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Jian He
Assignee: Jian He



The goal is to have YARN acl model pluggable so as to integrate other 
authorization tool such as Apache Ranger, Sentry.

Currently, we have 
- admin ACL
- queue ACL
- application ACL
- time line domain ACL
- service ACL

The proposal is to create a YarnAuthorizationProvider interface. Current 
implementation will be the default implementation. Ranger or Sentry plug-in can 
implement  this interface.

Benefit:
-  Unify the code base. With the default implementation, we can get rid of each 
specific ACL manager such as AdminAclManager, ApplicationACLsManager, 
QueueAclsManager etc.
- Enable Ranger, Sentry to do authorization for YARN. 



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

Success: YARN-3098 PreCommit Build #6426

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3098
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6426/

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




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

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

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
5e44c3e1a77303270ea6dbc11076cb072b61f8a7 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6425
Archived 15 artifacts
Archive block size is 32768
Received 63 blocks and 6786148 bytes
Compression is 23.3%
Took 1.9 sec
Description set: YARN-3098
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Re: How to edit contributor list

2015-01-26 Thread Wangda Tan 
Hi Karthik,
Can you add me to the list as well?

Thanks,
Wangda

On Mon, Jan 26, 2015 at 3:39 PM, Karthik Kambatla 
wrote:

> https://issues.apache.org/jira/plugins/servlet/project-config/YARN/roles
>
> Ravi - you already had permissions to add contributors. Tsuyoshi - I just
> added you.
>
> On Tue, Jan 27, 2015 at 1:26 AM, Ravi Prakash  wrote:
>
> > I too would like that capability. ~raviprak
> >
> >
> >  On Friday, January 23, 2015 11:27 AM, Tsuyoshi Ozawa <
> > oz...@apache.org> wrote:
> >
> >
> >  Hi,
> >
> > I'd like to edit contributor list to add new contributors. Does anyone
> > know how to do that?
> >
> > - Tsuyoshi
> >
> >
> >
> >
>
>
>
> --
> Karthik Kambatla
> Software Engineer, Cloudera Inc.
> 
> http://five.sentenc.es
>

Re: How to edit contributor list

2015-01-26 Thread Ravi Prakash 
Suuhhweeettt!! Thanks Karthik!
 

 On Monday, January 26, 2015 3:40 PM, Karthik Kambatla  
wrote:
   

 https://issues.apache.org/jira/plugins/servlet/project-config/YARN/roles

Ravi - you already had permissions to add contributors. Tsuyoshi - I just
added you.

On Tue, Jan 27, 2015 at 1:26 AM, Ravi Prakash  wrote:

> I too would like that capability. ~raviprak
>
>
>      On Friday, January 23, 2015 11:27 AM, Tsuyoshi Ozawa <
> oz...@apache.org> wrote:
>
>
>  Hi,
>
> I'd like to edit contributor list to add new contributors. Does anyone
> know how to do that?
>
> - Tsuyoshi
>
>
>
>



-- 
Karthik Kambatla
Software Engineer, Cloudera Inc.

http://five.sentenc.es

Failed: YARN-3098 PreCommit Build #6427

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3098
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6427/

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

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

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

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

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

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

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

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

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

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

  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore

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

This message is automatically generated.


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


Comment added.
19c60ec475b88b7136ac4e53d17e7e653c6baafe logged out


==
==
Finished build.
==
==


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



###
## FAILED TESTS (if any) 
##
1 tests failed.
REGRESSION:  
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry

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.assertFalse(Assert.java:64)
at org.junit.Assert.assertFalse(Assert.java:74)
at 
org.apache.hadoop.yarn.server.resourcemanager.recovery.TestFSRMStateStore.testFSRMStateStoreClientRetry(TestFSRMStateStore.java:289)

Failed: YARN-1743 PreCommit Build #6429

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1743
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6429/

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

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12694668/YARN-1743-3.patch
  against trunk revision 6f9fe76.

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

{color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

  {color:red}-1 javac{color}.  The applied patch generated 1188 javac 
compiler warnings (more than the trunk's current 1187 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-common 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6429//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/6429//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6429//console

This message is automatically generated.


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


Comment added.
7fadee83d3fdf500f2f0280dfd4851e0b5818c8e logged out


==
==
Finished build.
==
==


Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6426
Archived 21 artifacts
Archive block size is 32768
Received 49 blocks and 7471646 bytes
Compression is 17.7%
Took 1.7 sec
[description-setter] Could not determine description.
Recording test results
Publish JUnit test result report is waiting for a checkpoint on 
PreCommit-YARN-Build #6428
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
All tests passed

Success: YARN-3011 PreCommit Build #6430

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3011
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6430/

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



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

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

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

This message is automatically generated.


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


Comment added.
b4780c68f55962074b7025638d71230609cb6f2a logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6426
Archived 15 artifacts
Archive block size is 32768
Received 63 blocks and 6709528 bytes
Compression is 23.5%
Took 1.9 sec
Description set: YARN-3011
Recording test results
Publish JUnit test result report is waiting for a checkpoint on 
PreCommit-YARN-Build #6429
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

Success: YARN-3099 PreCommit Build #6428

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3099
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6428/

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




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

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

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
38dda93dc94ae89453a197c00f2e513c4098a778 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6426
Archived 15 artifacts
Archive block size is 32768
Received 63 blocks and 6786497 bytes
Compression is 23.3%
Took 1.4 sec
Description set: YARN-3099
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any) 
##
All tests passed

[jira] [Created] (YARN-3101) FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it

2015-01-26 Thread Anubhav Dhoot (JIRA) 
Anubhav Dhoot created YARN-3101:
---

 Summary: FairScheduler#fitInMaxShare was added to validate 
reservations but it does not consider it 
 Key: YARN-3101
 URL: https://issues.apache.org/jira/browse/YARN-3101
 Project: Hadoop YARN
  Issue Type: Bug
  Components: fairscheduler
Reporter: Anubhav Dhoot


YARN-2811 added fitInMaxShare to validate reservations on a queue, but did not 
count it during its calculations. It also had the condition reversed so the 
test was still passing because both cancelled each other. 



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

[jira] [Resolved] (YARN-2718) Create a CompositeConatainerExecutor that combines DockerContainerExecutor and DefaultContainerExecutor

2015-01-26 Thread Chris Douglas (JIRA) 

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

Chris Douglas resolved YARN-2718.
-
Resolution: Duplicate

Patch posted to YARN-1983; closing this

> Create a CompositeConatainerExecutor that combines DockerContainerExecutor 
> and DefaultContainerExecutor
> ---
>
> Key: YARN-2718
> URL: https://issues.apache.org/jira/browse/YARN-2718
> Project: Hadoop YARN
>  Issue Type: New Feature
>Reporter: Abin Shahab
> Attachments: YARN-2718.patch
>
>
> There should be a composite container that allows users to run their jobs in 
> DockerContainerExecutor, but switch to DefaultContainerExecutor for debugging 
> purposes.



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

Success: YARN-3079 PreCommit Build #6431

2015-01-26 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-3079
Build: https://builds.apache.org/job/PreCommit-YARN-Build/6431/

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
22c5a7c3157f9ea16fcfe17abaae859dd4d4 logged out


==
==
Finished build.
==
==


Archiving artifacts
Sending artifact delta relative to PreCommit-YARN-Build #6430
ERROR: Failed to archive 
{patchprocess/patchJavacWarnings.txt=patchprocess/patchJavacWarnings.txt, 
patchprocess/trunkJavacWarnings.txt=patchprocess/trunkJavacWarnings.txt, 
patchprocess/patchJavadocWarnings.txt=patchprocess/patchJavadocWarnings.txt, 
patchprocess/testrun_hadoop-kms.txt=patchprocess/testrun_hadoop-kms.txt, 
patchprocess/trunkJavadocWarnings.txt=patchprocess/trunkJavadocWarnings.txt, 
patchprocess/patchReleaseAuditOutput.txt=patchprocess/patchReleaseAuditOutput.txt,
 
patchprocess/patchReleaseAuditWarnings.txt=patchprocess/patchReleaseAuditWarnings.txt,
 
patchprocess/patchFindBugsOutputhadoop-kms.txt=patchprocess/patchFindBugsOutputhadoop-kms.txt,
 
patchprocess/filteredPatchJavacWarnings.txt=patchprocess/filteredPatchJavacWarnings.txt,
 patchprocess/patchEclipseOutput.txt=patchprocess/patchEclipseOutput.txt, 
patchprocess/patchFindbugsWarningshadoop-kms.xml=patchprocess/patchFindbugsWarningshadoop-kms.xml,
 patchprocess/diffJavadocWarnings.txt=patchprocess/diffJavadocWarnings.txt, 
patchprocess/filteredTrunkJavacWarnings.txt=patchprocess/filteredTrunkJavacWarnings.txt,
 
patchprocess/newPatchFindbugsWarningshadoop-kms.xml=patchprocess/newPatchFindbugsWarningshadoop-kms.xml,
 
patchprocess/newPatchFindbugsWarningshadoop-kms.html=patchprocess/newPatchFindbugsWarningshadoop-kms.html}
 due to internal error; falling back to full archiving
java.lang.IllegalStateException: checksum mismatch after transfer 
(6581801202181819975 vs. 3371887098); 
/x1/jenkins/jenkins-home/jobs/PreCommit-YARN-Build/builds/2015-01-27_07-20-31/archive/patchprocess/trunkJavacWarnings.txt
 may be corrupted
at jsync.protocol.FileSequenceReader.read(FileSequenceReader.java:45)
at 
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.remoteSync(JSyncArtifactManager.java:145)
at 
com.cloudbees.jenkins.plugins.jsync.archiver.JSyncArtifactManager.archive(JSyncArtifactManager.java:68)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1731)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:232)
Description set: YARN-3079
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###
## FAILED TESTS (if any)