Failed: YARN-2190 PreCommit Build #5915

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2190
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5915/

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

==
==
Testing patch for YARN-2190.
==
==


HEAD is now at 555fa2d HDFS-7403. Inaccurate javadoc of  BlockUCState#COMPLETE 
state. (Yongjun Zhang via yliu)
Previous HEAD position was 555fa2d... HDFS-7403. Inaccurate javadoc of  
BlockUCState#COMPLETE state. (Yongjun Zhang via yliu)
Switched to branch 'trunk'
Your branch is behind 'origin/trunk' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)
First, rewinding head to replay your work on top of it...
Fast-forwarded trunk to 555fa2d9d0dbb3bf2b209a953eb07a59bbfe3197.
YARN-2190 patch is being downloaded at Mon Nov 24 08:20:30 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12683290/YARN-2190.7.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/12683290/YARN-2190.7.patch
  against trunk revision 555fa2d.

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

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

This message is automatically generated.


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


Comment added.
0f755eca95091dd0fdafa7ca1b9dbafa5b311d71 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.

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

2014-11-24 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/15/

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

Running org.apache.hadoop.yarn.client.TestResourceTrackerOnHA
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.022 sec - in 
org.apache.hadoop.yarn.client.TestResourceTrackerOnHA

Results :

Tests in error: 
  TestApplicationClientProtocolOnHA.testGetContainersOnHA:154 » Connect Call 
Fro...
  TestApplicationClientProtocolOnHA.testGetApplicationAttemptReportOnHA:128 » 
Connect

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

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-yarn ... SUCCESS [  3.059 s]
[INFO] hadoop-yarn-api ... SUCCESS [02:47 min]
[INFO] hadoop-yarn-common  SUCCESS [02:24 min]
[INFO] hadoop-yarn-server  SUCCESS [  0.079 s]
[INFO] hadoop-yarn-server-common . SUCCESS [ 38.817 s]
[INFO] hadoop-yarn-server-nodemanager  SUCCESS [05:57 min]
[INFO] hadoop-yarn-server-web-proxy .. SUCCESS [ 17.418 s]
[INFO] hadoop-yarn-server-applicationhistoryservice .. SUCCESS [02:51 min]
[INFO] hadoop-yarn-server-resourcemanager  SUCCESS [46:46 min]
[INFO] hadoop-yarn-server-tests .. SUCCESS [02:12 min]
[INFO] hadoop-yarn-client  FAILURE [07:13 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:11 h
[INFO] Finished at: 2014-11-24T11:43:19+00:00
[INFO] Final Memory: 94M/928M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.16: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-Java8/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
Updating HDFS-7403
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure
Sending email for trigger: Failure



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

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

2014-11-24 Thread Apache Jenkins Server 
See 

Changes:

[yliu] HDFS-7403. Inaccurate javadoc of  BlockUCState#COMPLETE state. (Yongjun 
Zhang via yliu)

--
[...truncated 9141 lines...]
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.3: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.6.0_45
Building tree for all the packages and classes...
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating

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

2014-11-24 Thread Apache Jenkins Server 
See

Re: [QUESTION] Allocating a full YARN cluster

2014-11-24 Thread Robert Metzger 
Hi Ravi,

thanks for you reply. I have two screenshots that show the nodes and the
scheduler output:

Nodes: http://img42.com/gfrGH
Scheduler: http://img42.com/6i8x8

Maybe I'm doing something wrong in my code. The screenshots indicate that
the scheduler assigned the resources to my AppicationMaster but it does not
allocate the container.
The only thing I'm doing in my code is rmClient.allocate(0) and
response.getAllocatedContainers() until all containers are allocated. But
my code is not getting the response for the last container.
Is there anything else that I have to do in the Application Master? Are
there any logfiles you suggest looking into?

Best,
Robert


On Fri, Nov 21, 2014 at 12:03 AM, Ravi Prakash  wrote:

> Hi Robert!
> Do you see a nodemanager really with 46Gb free in the web ui (
> http://resourcemanager:8088/cluster/nodes) ? How big is your
> ApplicationMaster itself (because that too is launched in a container).
> What happens if you ask for, say 30Gb containers?
> CheersRavi
>
>
>  On Thursday, November 20, 2014 3:48 AM, Robert Metzger <
> rmetz...@apache.org> wrote:
>
>
>  Hi,
>
> I'm a developer of Apache Flink (incubating). Flink has a YARN client that
> allows users to start Flink in their YARN cluster. The current
> implementation is not doing fine-grained resource isolation. We just
> allocate our master and worker nodes within YARN and keep them running
> until the user stops the cluster again.
>
> The issue I'm facing is that I can not allocate all containers in my YARN
> cluster.
>
>
> My cluster has 42 nodes with 46.09 GB each (according to the NodeManager)
> If my Flink client is requesting 41 + 1 (workers + master) containers (with
> 46GB each), I'm only getting 41 containers (instead of 42).
> My ApplicationMaster is sending allocate requests until all worker nodes
> have been started.
>
> AllocateResponse response = rmClient.allocate(0);
> for (Container container : response.getAllocatedContainers()) ...
>
> My code is never getting the allocation response for the last container
> from YARN, even though one NodeManager in the cluster is free.
>
> Is there anything that I'm doing wrong here? How can I resolve the issue?
>
>
> Another question: Some of our users were reporting issues with (worker)
> containers keep running once the Flink YARN session has been stopped. The
> NodeManagers were reporting that no containers were running but "jps"
> showed that the JVMs were still there.
> I tried to reproduce the issue on Amazon EMR which was impossible, but on
> Google Compute Cloud (HD 2.4.1) I was also seeing the issue.
> Is this a configuration / YARN version issue?
> Am I as a YARN application supposed to kill my own JVMs or is YARN doing
> that for me?
>
>
> Cheers,
> Robert
>
>
>
>

[jira] [Created] (YARN-2894) Disallow binding of aclManagers while starting RMWebApp

2014-11-24 Thread Rohith (JIRA) 
Rohith created YARN-2894:


 Summary: Disallow binding of aclManagers while starting RMWebApp
 Key: YARN-2894
 URL: https://issues.apache.org/jira/browse/YARN-2894
 Project: Hadoop YARN
  Issue Type: Bug
  Components: resourcemanager
Affects Versions: 2.6.0
Reporter: Rohith
Assignee: Rohith
 Fix For: 2.7.0


Binding aclManager to RMWebApp would cause problem if RM is switched. There 
could be some validation check may fail.
I think , we should not bind aclManager for RMWebApp, instead we should get 
from RM instance.
In RMWebApp,
{code}
if (rm != null) {
  bind(ResourceManager.class).toInstance(rm);
  bind(RMContext.class).toInstance(rm.getRMContext());
  bind(ApplicationACLsManager.class).toInstance(
  rm.getApplicationACLsManager());
  bind(QueueACLsManager.class).toInstance(rm.getQueueACLsManager());
}
{code}

and in AppBlock#render below check may fail(Need to test and confirm)
{code}
   if (callerUGI != null
&& !(this.aclsManager.checkAccess(callerUGI,
ApplicationAccessType.VIEW_APP, app.getUser(), appID) ||
 this.queueACLsManager.checkAccess(callerUGI,
QueueACL.ADMINISTER_QUEUE, app.getQueue( {
  puts("You (User " + remoteUser
  + ") are not authorized to view application " + appID);
  return;
}
{code}



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

[jira] [Created] (YARN-2895) Integrate distributed scheduling with capacity scheduler

2014-11-24 Thread Wangda Tan (JIRA) 
Wangda Tan created YARN-2895:


 Summary: Integrate distributed scheduling with capacity scheduler
 Key: YARN-2895
 URL: https://issues.apache.org/jira/browse/YARN-2895
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: capacityscheduler, resourcemanager, scheduler
Reporter: Wangda Tan
Assignee: Wangda Tan


There're some benefit to integrate distributed scheduling mechanism (LocalRM) 
with capacity scheduler:
- Resource usage of opportunistic container can be tracked by central RM and 
capacity could be enforced
- Opportunity to transfer opportunistic container to conservative container 



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

[jira] [Created] (YARN-2896) Server side PB changes for Priority Label Manager and Admin CLI support

2014-11-24 Thread Sunil G (JIRA) 
Sunil G created YARN-2896:
-

 Summary: Server side PB changes for Priority Label Manager and 
Admin CLI support
 Key: YARN-2896
 URL: https://issues.apache.org/jira/browse/YARN-2896
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Sunil G
Assignee: Sunil G






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

Failed: YARN-2025 PreCommit Build #5916

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2025
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5916/

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


==
==
Testing patch for YARN-2025.
==
==


HEAD is now at 555fa2d HDFS-7403. Inaccurate javadoc of  BlockUCState#COMPLETE 
state. (Yongjun Zhang via yliu)
Switched to branch 'trunk'
Your branch is up-to-date with 'origin/trunk'.
Current branch trunk is up to date.
YARN-2025 patch is being downloaded at Mon Nov 24 17:10:33 UTC 2014 from
http://issues.apache.org/jira/secure/attachment/12643596/YARN-2025.1.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/12643596/YARN-2025.1.patch
  against trunk revision 555fa2d.

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

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

This message is automatically generated.


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


Comment added.
297eee9e64d0adfe488c35aa07b783f2210a9ec9 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-2897) CrossOriginFilter needs more log statements

2014-11-24 Thread Mit Desai (JIRA) 
Mit Desai created YARN-2897:
---

 Summary: CrossOriginFilter needs more log statements
 Key: YARN-2897
 URL: https://issues.apache.org/jira/browse/YARN-2897
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Mit Desai
Assignee: Mit Desai


CrossOriginFilter does not log as mcch to make debugging easier



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

[jira] [Resolved] (YARN-2898) Contaniner-executor prints out wrong error information when failed

2014-11-24 Thread Jason Lowe (JIRA) 

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

Jason Lowe resolved YARN-2898.
--
Resolution: Duplicate

This is a duplicate of YAN-2847.

> Contaniner-executor prints out wrong error information when failed
> --
>
> Key: YARN-2898
> URL: https://issues.apache.org/jira/browse/YARN-2898
> Project: Hadoop YARN
>  Issue Type: Bug
>Reporter: Wei Yan
>Assignee: Wei Yan
>Priority: Minor
> Attachments: YARN-2898-1.patch
>
>
> *Settings*: YARN cluster using LinuxContainerExecutor, and the "banned.users" 
> is left empty in the container-executor.cfg. The default banned list is 
> \{"mapred", "hdfs", "bin"\}.
> *Problem*: let user "mapred" submit a job, it will fail with 
> "ExitCodeException exitCode=139", which is segment fault. This is incorrect, 
> and the correct information should be "Requested user mapred is banned".



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

Failed: YARN-1984 PreCommit Build #5918

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1984
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5918/

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

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

This message is automatically generated.


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


Comment added.
ca3db00eb3e1478a4bb04e5b904df1b264e57209 logged out


==
==
Finished build.
==
==


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



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

[jira] [Created] (YARN-2898) Contaniner-executor may fail with wrong information

2014-11-24 Thread Wei Yan (JIRA) 
Wei Yan created YARN-2898:
-

 Summary: Contaniner-executor may fail with wrong information
 Key: YARN-2898
 URL: https://issues.apache.org/jira/browse/YARN-2898
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Wei Yan
Assignee: Wei Yan
Priority: Minor


*Settings*: YARN cluster using LinuxContainerExecutor, and the "banned.users" 
is left empty in the container-executor.cfg. The default banned list is 
\{"mapred", "hdfs", "bin"\}.

*Problem*: let user "mapred" submit a job, it will fail with "ExitCodeException 
exitCode=139", which is segment fault. This is incorrect, and the correct 
information should be "Requested user mapred is banned".





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

Failed: YARN-2897 PreCommit Build #5922

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2897
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5922/

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


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


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




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

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

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

This message is automatically generated.


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


Comment added.
32ec89cf433bb4ec01820ecde6a5f1d06e5035d4 logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-1984 PreCommit Build #5919

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1984
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5919/

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

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

This message is automatically generated.


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


Comment added.
379a2cb410cdd4d3d0cb447044c8729a74b2 logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2637 PreCommit Build #5917

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2637
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5917/

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

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

{color:green}+1 tests included{color}.  The patch appears to include 13 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/5917//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5917//console

This message is automatically generated.


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


Comment added.
14eb10ce4fc60e67334425cbb05f68744afb8e9d logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2762 PreCommit Build #5920

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2762
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5920/

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




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

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

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

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

This message is automatically generated.


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


Comment added.
dd8a16692b0ef275c308a8cddcf6acb7339d770a 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 ?*.*? 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-1984 PreCommit Build #5921

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1984
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5921/

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

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

This message is automatically generated.


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


Comment added.
97f9e4b69618ea7d3c90ca92437cd5c5eddc6eda logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2691 PreCommit Build #5923

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2691
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5923/

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

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

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

  {color:red}-1 javac{color}.  The applied patch generated 1229 javac 
compiler warnings (more than the trunk's current 1219 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/5923//testReport/
Javac warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/5923//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5923//console

This message is automatically generated.


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


Comment added.
59296b5a22618a91f30b210939dde16d55eb03bc logged out


==
==
Finished build.
==
==


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



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

[jira] [Created] (YARN-2899) Run TestDockerContainerExecutorWithMocks on Linux only

2014-11-24 Thread Ming Ma (JIRA) 
Ming Ma created YARN-2899:
-

 Summary: Run TestDockerContainerExecutorWithMocks on Linux only
 Key: YARN-2899
 URL: https://issues.apache.org/jira/browse/YARN-2899
 Project: Hadoop YARN
  Issue Type: Bug
Reporter: Ming Ma
Priority: Minor


It seems the test should strictly check for Linux, otherwise, it will fail when 
the OS isn't Linux.



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

[jira] [Created] (YARN-2900) Application Not Found in AHS throws Internal Server Error with NPE

2014-11-24 Thread Jonathan Eagles (JIRA) 
Jonathan Eagles created YARN-2900:
-

 Summary: Application Not Found in AHS throws Internal Server Error 
with NPE
 Key: YARN-2900
 URL: https://issues.apache.org/jira/browse/YARN-2900
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Jonathan Eagles
Assignee: Mit Desai






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

Failed: YARN-2899 PreCommit Build #5924

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2899
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5924/

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

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

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

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

This message is automatically generated.


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


Comment added.
e0893b4b9458cf8e09ede3c5d3ece4cd2787abbb logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2900 PreCommit Build #5926

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2900
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5926/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3124 lines...]
  http://issues.apache.org/jira/secure/attachment/12683426/YARN-2900.patch
  against trunk revision 2967c17.

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

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

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

This message is automatically generated.


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


Comment added.
249bb59d98123e14ca81948c30ede541393e6f26 logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2188 PreCommit Build #5925

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2188
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5925/

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

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

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

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

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

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

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

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

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

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

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

This message is automatically generated.


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


Comment added.
107fb44496955bf8d693c8601520e888f6228ebf logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-1996 PreCommit Build #5927

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-1996
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5927/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 3759 lines...]
  against trunk revision 8caf537.

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

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

  {color:red}-1 javac{color}.  The applied patch generated 1223 javac 
compiler warnings (more than the trunk's current 1219 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-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app 
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

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

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

This message is automatically generated.


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


Comment added.
71ab155d43cbfaaf8c81bd5f1ca5f16e201d84ed logged out


==
==
Finished build.
==
==


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



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

Failed: YARN-2637 PreCommit Build #5928

2014-11-24 Thread Apache Jenkins Server 
Jira: https://issues.apache.org/jira/browse/YARN-2637
Build: https://builds.apache.org/job/PreCommit-YARN-Build/5928/

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

{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.webapp.TestRMWebServicesCapacitySched
  
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestContainerAllocation
  
org.apache.hadoop.yarn.server.resourcemanager.TestApplicationMasterService

  The following test timeouts occurred in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification

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

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

This message is automatically generated.


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


Comment added.
904602ff95b13a34e61ef09f78f9c4984f576100 logged out


==
==
Finished build.
==
==


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



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