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

2016-06-13 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1574/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69073 lines...]
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop YARN . SUCCESS [  4.764 s]
[INFO] Apache Hadoop YARN API . SUCCESS [01:34 min]
[INFO] Apache Hadoop YARN Common .. SUCCESS [03:22 min]
[INFO] Apache Hadoop YARN Server .. SUCCESS [  0.553 s]
[INFO] Apache Hadoop YARN Server Common ... SUCCESS [ 43.153 s]
[INFO] Apache Hadoop YARN NodeManager . SUCCESS [14:15 min]
[INFO] Apache Hadoop YARN Web Proxy ... SUCCESS [ 26.545 s]
[INFO] Apache Hadoop YARN ApplicationHistoryService ... SUCCESS [03:33 min]
[INFO] Apache Hadoop YARN ResourceManager . SUCCESS [40:31 min]
[INFO] Apache Hadoop YARN Server Tests  SUCCESS [02:16 min]
[INFO] Apache Hadoop YARN Client .. FAILURE [07:48 min]
[INFO] Apache Hadoop YARN SharedCacheManager .. SKIPPED
[INFO] Apache Hadoop YARN Timeline Plugin Storage . SKIPPED
[INFO] Apache Hadoop YARN Applications  SUCCESS [  0.533 s]
[INFO] Apache Hadoop YARN DistributedShell  SKIPPED
[INFO] Apache Hadoop YARN Unmanaged Am Launcher ... SKIPPED
[INFO] Apache Hadoop YARN Site  SUCCESS [  0.507 s]
[INFO] Apache Hadoop YARN Registry  SUCCESS [01:03 min]
[INFO] Apache Hadoop YARN Project . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:15 h
[INFO] Finished at: 2016-06-14T02:53:11+00:00
[INFO] Final Memory: 149M/3584M
[INFO] 
[WARNING] The requested profile "parallel-tests" could not be activated because 
it does not exist.
[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-Java8/source/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
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Recording test results
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.hadoop.yarn.client.api.impl.TestYarnClient.testUpdateReservation

Error Message:
Exhausted attempts in checking if node capacity was added to the plan

Stack Trace:
java.lang.AssertionError: Exhausted attempts in checking if node capacity was 
added to the plan
at org.junit.Assert.fail(Assert.java:88)
at

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

2016-06-13 Thread Apache Jenkins Server 
See 

Changes:

[aajisaka] HADOOP-13270. BZip2CompressionInputStream finds the same compression

--
[...truncated 68876 lines...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Building index for all the packages and classes...
Generating 

Generating 

Generating 

Building index for all classes...
Generating 

Generating 

Generating 

Generating 

Generating 

52 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:73:
 warning: no description for @throws
[WARNING] * @throws Exception
[WARNING] ^
[WARNING] 
:174:
 warning: no description for @throws
[WARNING] * @throws IOException
[WARNING] ^
[WARNING]

Re: [DISCUSS] Increased use of feature branches

2016-06-13 Thread Karthik Kambatla 
Thanks for clarifying Andrew. Inline.

On Mon, Jun 13, 2016 at 3:59 PM, Andrew Wang 
wrote:

>
> On Fri, Jun 10, 2016 at 9:39 PM, Karthik Kambatla 
> wrote:
>
>> I would like to understand the trunk-incompat part of the proposal a
>> little better.
>>
>> Is trunk-incompat always going to be a superset of trunk? If yes, is it
>> just a change in naming convention with a hope that our approach to trunk
>> stability changes as Sangjin mentioned?
>>
>> Or, is it okay for trunk-incompat to be based off of an older commit in
>> trunk with (in)frequent rebases? This has the risk of incompatible changes
>> truly rotting. Periodic rebases will ensure these changes don't rot while
>> also easing the burden of hosting two branches; if we choose this route,
>> some guidance of the period and who rebases will be nice.
>>
>
> Based on my understanding from Vinod on the previous "Looking to..."
> thread, it would be the latter. The goal of trunk-incompat was to avoid
> adding yet-another-branch we need to commit to every time, compared to the
> branch-3 proposal.
>
> I agree with the concerns you raise around feature rot. For a feature like
> EC, it'd be untenable to leave it in trunk-incompat since the rebases would
> be impossible. I imagine we'd also need a very motivated maintainer (or
> maintainers) to handle the periodic integration of new trunk commits, since
> you'd potentially be doing it for multiple large features. If some brave
> and experienced committer is willing to own maintenance of the
> trunk-incompat branch, I think it could work. However, this is a big shift
> from how we've historically done development.
>

If an incompatible feature is ready (like EC here), should we consider
working towards the next major release? In other words, is it okay to defer
cutting branch-3 until we have a large incompatible feature that would be a
pain to keep up with?


>
> This is why I leaned toward Chris D's proposal, which is that we cut
> branch-3 for 3.0.0-beta1, at which point trunk moves on to 4.0. In my mind,
> this is the "default" proposal, since it's how we've previously done
> things, with the slight adjustment that we defer cutting branch-3 until we
> start enforcing compatibility. This is my current plan for the Hadoop 3
> series, and we already had a lot of +1's about releasing from trunk on the
> previous thread.
>

I guess this makes sense.


>
> If there's a strong advocate for trunk-incompat over branch-3, let's have
> that discussion. However, given that beta is still months (and multiple
> releases) away, I don't think this decision affects my near-term goal of
> getting 3.0.0-alpha1 released.
>
> Thanks,
> Andrew
>

Re: [DISCUSS] Increased use of feature branches

2016-06-13 Thread Andrew Wang 
On Fri, Jun 10, 2016 at 9:39 PM, Karthik Kambatla 
wrote:

> I would like to understand the trunk-incompat part of the proposal a
> little better.
>
> Is trunk-incompat always going to be a superset of trunk? If yes, is it
> just a change in naming convention with a hope that our approach to trunk
> stability changes as Sangjin mentioned?
>
> Or, is it okay for trunk-incompat to be based off of an older commit in
> trunk with (in)frequent rebases? This has the risk of incompatible changes
> truly rotting. Periodic rebases will ensure these changes don't rot while
> also easing the burden of hosting two branches; if we choose this route,
> some guidance of the period and who rebases will be nice.
>

Based on my understanding from Vinod on the previous "Looking to..."
thread, it would be the latter. The goal of trunk-incompat was to avoid
adding yet-another-branch we need to commit to every time, compared to the
branch-3 proposal.

I agree with the concerns you raise around feature rot. For a feature like
EC, it'd be untenable to leave it in trunk-incompat since the rebases would
be impossible. I imagine we'd also need a very motivated maintainer (or
maintainers) to handle the periodic integration of new trunk commits, since
you'd potentially be doing it for multiple large features. If some brave
and experienced committer is willing to own maintenance of the
trunk-incompat branch, I think it could work. However, this is a big shift
from how we've historically done development.

This is why I leaned toward Chris D's proposal, which is that we cut
branch-3 for 3.0.0-beta1, at which point trunk moves on to 4.0. In my mind,
this is the "default" proposal, since it's how we've previously done
things, with the slight adjustment that we defer cutting branch-3 until we
start enforcing compatibility. This is my current plan for the Hadoop 3
series, and we already had a lot of +1's about releasing from trunk on the
previous thread.

If there's a strong advocate for trunk-incompat over branch-3, let's have
that discussion. However, given that beta is still months (and multiple
releases) away, I don't think this decision affects my near-term goal of
getting 3.0.0-alpha1 released.

Thanks,
Andrew

[jira] [Created] (YARN-5245) [YARN-3368] Add nodes heatmap chart

2016-06-13 Thread Wangda Tan (JIRA) 
Wangda Tan created YARN-5245:


 Summary: [YARN-3368] Add nodes heatmap chart
 Key: YARN-5245
 URL: https://issues.apache.org/jira/browse/YARN-5245
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Wangda Tan
Assignee: Wangda Tan


It gonna be very helpful to add heat map chart to get overall cluster resource 
usage of nodes.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

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

2016-06-13 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1573/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 65482 lines...]
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop YARN . SUCCESS [  4.948 s]
[INFO] Apache Hadoop YARN API . SUCCESS [01:36 min]
[INFO] Apache Hadoop YARN Common .. SUCCESS [03:27 min]
[INFO] Apache Hadoop YARN Server .. SUCCESS [  0.529 s]
[INFO] Apache Hadoop YARN Server Common ... SUCCESS [ 44.998 s]
[INFO] Apache Hadoop YARN NodeManager . FAILURE [13:05 min]
[INFO] Apache Hadoop YARN Web Proxy ... SUCCESS [ 24.169 s]
[INFO] Apache Hadoop YARN ApplicationHistoryService ... SUCCESS [03:22 min]
[INFO] Apache Hadoop YARN ResourceManager . SUCCESS [37:00 min]
[INFO] Apache Hadoop YARN Server Tests  SKIPPED
[INFO] Apache Hadoop YARN Client .. SKIPPED
[INFO] Apache Hadoop YARN SharedCacheManager .. SKIPPED
[INFO] Apache Hadoop YARN Timeline Plugin Storage . SKIPPED
[INFO] Apache Hadoop YARN Applications  SUCCESS [  0.443 s]
[INFO] Apache Hadoop YARN DistributedShell  SKIPPED
[INFO] Apache Hadoop YARN Unmanaged Am Launcher ... SKIPPED
[INFO] Apache Hadoop YARN Site  SUCCESS [  0.426 s]
[INFO] Apache Hadoop YARN Registry  SUCCESS [ 53.686 s]
[INFO] Apache Hadoop YARN Project . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:00 h
[INFO] Finished at: 2016-06-13T20:38:13+00:00
[INFO] Final Memory: 135M/3700M
[INFO] 
[WARNING] The requested profile "parallel-tests" could not be activated because 
it does not exist.
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project hadoop-yarn-server-nodemanager: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Yarn-trunk-Java8/source/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/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-nodemanager
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Recording test results
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.hadoop.yarn.server.nodemanager.containermanager.queuing.TestQueuingContainerManager.testKillMultipleOpportunisticContainers

Error Message:
ContainerState is not correct (timedout) expected: but 
was:

Stack Trace:
java.lang.AssertionError: ContainerState is not correct (timedout) 
expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at

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

2016-06-13 Thread Apache Jenkins Server 
See 

Changes:

[wang] HADOOP-13079. Add -q option to Ls to print ? instead of non-printable

[wang] HDFS-10516. Fix bug when warming up EDEK cache of more than one

--
[...truncated 65285 lines...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Building index for all the packages and classes...
Generating 

Generating 

Generating 

Building index for all classes...
Generating 

Generating 

Generating 

Generating 

Generating 

52 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:73:
 warning: no description for @throws
[WARNING] * @throws Exception
[WARNING] ^
[WARNING] 
:174:
 warning: no description for @throws
[WARNING] * @throws IOException
[WARNING] ^
[WARNING]

[jira] [Created] (YARN-5244) Documentation required for DNS Server implementation

2016-06-13 Thread Jonathan Maron (JIRA) 
Jonathan Maron created YARN-5244:


 Summary: Documentation required for DNS Server implementation
 Key: YARN-5244
 URL: https://issues.apache.org/jira/browse/YARN-5244
 Project: Hadoop YARN
  Issue Type: Sub-task
Reporter: Jonathan Maron


The DNS server requires documentation describing its functionality etc



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Created] (YARN-5243) fix several rebase and other miscellaneous issues before merge

2016-06-13 Thread Sangjin Lee (JIRA) 
Sangjin Lee created YARN-5243:
-

 Summary: fix several rebase and other miscellaneous issues before 
merge
 Key: YARN-5243
 URL: https://issues.apache.org/jira/browse/YARN-5243
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: timelineserver
Affects Versions: YARN-2928
Reporter: Sangjin Lee
Assignee: Sangjin Lee


I have come across a couple of miscellaneous issues while inspecting the diffs 
against the trunk.

We also need to review one last time (probably after the final rebase) to 
ensure the timeline services v.2 leaves no impact when disabled.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Resolved] (YARN-5239) Eliminate unused imports checkstyle warnings

2016-06-13 Thread Joep Rottinghuis (JIRA) 

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

Joep Rottinghuis resolved YARN-5239.

Resolution: Won't Fix

> Eliminate unused imports checkstyle warnings
> 
>
> Key: YARN-5239
> URL: https://issues.apache.org/jira/browse/YARN-5239
> Project: Hadoop YARN
>  Issue Type: Sub-task
>  Components: timelineserver
>Affects Versions: YARN-2928
>Reporter: Joep Rottinghuis
>Assignee: Joep Rottinghuis
>Priority: Trivial
>  Labels: yarn-2928-1st-milestone
> Attachments: YARN-5239-YARN-2928.01.patch
>
>
> There are ~8 existing checkstyle issues generated due to unused imports.
> By fully qualifying the classes in javadoc and manually wrapping the javadoc 
> under 80 characters we can eliminate these warnings.
> This will help with the eventual merge because then we introduce 8 fewer 
> checkstyle warnings.
> The only checkstyle warnings left are now too many arguments, which cannot be 
> easily refactored w/o changing code structure.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Created] (YARN-5242) Update DominantResourceCalculator to consider all resource types in calculations

2016-06-13 Thread Varun Vasudev (JIRA) 
Varun Vasudev created YARN-5242:
---

 Summary: Update DominantResourceCalculator to consider all 
resource types in calculations
 Key: YARN-5242
 URL: https://issues.apache.org/jira/browse/YARN-5242
 Project: Hadoop YARN
  Issue Type: Sub-task
  Components: resourcemanager
Reporter: Varun Vasudev
Assignee: Varun Vasudev


The fitsIn function in the DominantResourceCalculator only looks at memory and 
cpu. It should be modified to use all available resource types.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Created] (YARN-5241) FairScheduler repeat container completed

2016-06-13 Thread ChenFolin (JIRA) 
ChenFolin created YARN-5241:
---

 Summary: FairScheduler repeat container completed
 Key: YARN-5241
 URL: https://issues.apache.org/jira/browse/YARN-5241
 Project: Hadoop YARN
  Issue Type: Bug
  Components: fairscheduler
Affects Versions: 2.7.2, 2.6.1, 2.5.0, 2.8.0
Reporter: ChenFolin


NodeManager heartbeat event NODE_UPDATE and ApplicationMaster allocate operate 
may cause repeat container completed, it can lead something wrong.

Node releaseContainer can pervent repeat release operate:
like:
public synchronized void releaseContainer(Container container) {
if (!isValidContainer(container.getId())) {
  LOG.error("Invalid container released " + container);
  return;
}

FSAppAttempt containerCompleted did not prevent repeat container completed 
operate.

Detail logs at attach file.



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

2016-06-13 Thread Apache Jenkins Server 
For more details, see 
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/61/

[Jun 12, 2016 4:42:38 PM] (Arun Suresh) YARN-5124. Modify AMRMClient to set the 
ExecutionType in the
[Jun 12, 2016 5:05:37 PM] (Arun Suresh) YARN-5212. Run existing 
ContainerManager tests using
[Jun 12, 2016 9:12:31 PM] (kasha) HADOOP-13243. 
TestRollingFileSystemSink.testSetInitialFlushTime() fails
[Jun 13, 2016 5:39:32 AM] (rohithsharmaks) YARN-4989. 
TestWorkPreservingRMRestart#testCapacitySchedulerRecovery


[Error replacing 'FILE' - Workspace is not accessible]

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

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

2016-06-13 Thread Apache Jenkins Server 
See https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/1572/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 69068 lines...]
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Hadoop YARN . SUCCESS [  4.816 s]
[INFO] Apache Hadoop YARN API . SUCCESS [01:35 min]
[INFO] Apache Hadoop YARN Common .. SUCCESS [03:21 min]
[INFO] Apache Hadoop YARN Server .. SUCCESS [  0.523 s]
[INFO] Apache Hadoop YARN Server Common ... SUCCESS [ 43.961 s]
[INFO] Apache Hadoop YARN NodeManager . SUCCESS [13:31 min]
[INFO] Apache Hadoop YARN Web Proxy ... SUCCESS [ 21.559 s]
[INFO] Apache Hadoop YARN ApplicationHistoryService ... SUCCESS [03:12 min]
[INFO] Apache Hadoop YARN ResourceManager . SUCCESS [36:02 min]
[INFO] Apache Hadoop YARN Server Tests  SUCCESS [02:07 min]
[INFO] Apache Hadoop YARN Client .. FAILURE [07:26 min]
[INFO] Apache Hadoop YARN SharedCacheManager .. SKIPPED
[INFO] Apache Hadoop YARN Timeline Plugin Storage . SKIPPED
[INFO] Apache Hadoop YARN Applications  SUCCESS [  0.457 s]
[INFO] Apache Hadoop YARN DistributedShell  SKIPPED
[INFO] Apache Hadoop YARN Unmanaged Am Launcher ... SKIPPED
[INFO] Apache Hadoop YARN Site  SUCCESS [  0.451 s]
[INFO] Apache Hadoop YARN Registry  SUCCESS [ 50.606 s]
[INFO] Apache Hadoop YARN Project . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:09 h
[INFO] Finished at: 2016-06-13T07:46:50+00:00
[INFO] Final Memory: 148M/3616M
[INFO] 
[WARNING] The requested profile "parallel-tests" could not be activated because 
it does not exist.
[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-Java8/source/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
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Recording test results
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Sending e-mails to: yarn-dev@hadoop.apache.org
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3
Setting 
LATEST1_8_HOME=/home/jenkins/jenkins-slave/tools/hudson.model.JDK/latest1.8
Setting 
MAVEN_3_3_3_HOME=/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/maven-3.3.3



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  org.apache.hadoop.yarn.client.cli.TestLogsCLI.testFetchApplictionLogs

Error Message:
expected:<[Hello]> but was:<[=]>

Stack Trace:
org.junit.ComparisonFailure: expected:<[Hello]> but was:<[=]>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at

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

2016-06-13 Thread Apache Jenkins Server 
See 

Changes:

[rohithsharmaks] YARN-4989. 
TestWorkPreservingRMRestart#testCapacitySchedulerRecovery

--
[...truncated 68871 lines...]
Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Generating 

Building index for all the packages and classes...
Generating 

Generating 

Generating 

Building index for all classes...
Generating 

Generating 

Generating 

Generating 

Generating 

52 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:73:
 warning: no description for @throws
[WARNING] * @throws Exception
[WARNING] ^
[WARNING] 
:174:
 warning: no description for @throws
[WARNING] * @throws IOException
[WARNING] ^
[WARNING]

[jira] [Resolved] (YARN-3455) Document CGroup support

2016-06-13 Thread Rohith Sharma K S (JIRA) 

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

Rohith Sharma K S resolved YARN-3455.
-
Resolution: Duplicate

> Document CGroup support 
> 
>
> Key: YARN-3455
> URL: https://issues.apache.org/jira/browse/YARN-3455
> Project: Hadoop YARN
>  Issue Type: Task
>  Components: documentation
>Reporter: Rohith Sharma K S
>
> It would be very useful if CGroup support is documented having sections like 
> below
> # Introduction
> # Configuring CGroups
> # Any specific configuration that controls CPU scheduling
> # How/when to use CGroups with some use case expanations



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Resolved] (YARN-1005) Log aggregators should check for FSDataOutputStream close before renaming to aggregated file.

2016-06-13 Thread Rohith Sharma K S (JIRA) 

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

Rohith Sharma K S resolved YARN-1005.
-
Resolution: Cannot Reproduce

> Log aggregators should check for FSDataOutputStream close before renaming to 
> aggregated file.
> -
>
> Key: YARN-1005
> URL: https://issues.apache.org/jira/browse/YARN-1005
> Project: Hadoop YARN
>  Issue Type: Bug
>  Components: nodemanager
>Affects Versions: 2.1.0-beta, 2.0.5-alpha
>Reporter: Rohith Sharma K S
>
> If AggregatedLogFormat.LogWriter.closeWriter() is interuppted, then 
> "remoteNodeTmpLogFileForApp" is renamed to "remoteNodeLogFileForApp" file. 
> This renamed file does not contain valid aggregated logs. There can be 
> situation renamed file can be not in BCFile format. 
> This cause issue while viewing from JobHistoryServer web page.
> {noformat}
> 2013-07-27 18:51:14,787 ERROR org.apache.hadoop.yarn.webapp.View: Error 
> getting logs for job_1374918614757_0002
> java.io.IOException: Not a valid BCFile.
>   at 
> org.apache.hadoop.io.file.tfile.BCFile$Magic.readAndVerify(BCFile.java:927)
>   at org.apache.hadoop.io.file.tfile.BCFile$Reader.(BCFile.java:628)
>   at org.apache.hadoop.io.file.tfile.TFile$Reader.(TFile.java:804)
>   at 
> org.apache.hadoop.yarn.logaggregation.AggregatedLogFormat$LogReader.(AggregatedLogFormat.java:337)
>   at 
> org.apache.hadoop.yarn.webapp.log.AggregatedLogsBlock.render(AggregatedLogsBlock.java:89)
>   at 
> org.apache.hadoop.yarn.webapp.view.HtmlBlock.render(HtmlBlock.java:64)
>   at 
> org.apache.hadoop.yarn.webapp.view.HtmlBlock.renderPartial(HtmlBlock.java:74)
> {noformat}
>  



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org

[jira] [Resolved] (YARN-4627) TestRMWebServicesAppsModification fails with BindException

2016-06-13 Thread Rohith Sharma K S (JIRA) 

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

Rohith Sharma K S resolved YARN-4627.
-
Resolution: Duplicate

> TestRMWebServicesAppsModification fails with BindException
> --
>
> Key: YARN-4627
> URL: https://issues.apache.org/jira/browse/YARN-4627
> Project: Hadoop YARN
>  Issue Type: Test
>  Components: test
>Reporter: Rohith Sharma K S
>
> In the build 
> [report|https://builds.apache.org/job/PreCommit-YARN-Build/10367/artifact/patchprocess/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-resourcemanager-jdk1.8.0_66.txt]
>  , TestRMWebServicesAppsModification fails with BindExceptions.
> {noformat}
> Running 
> org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification
> Tests run: 44, Failures: 0, Errors: 27, Skipped: 0, Time elapsed: 90.028 sec 
> <<< FAILURE! - in 
> org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification
> testSingleAppKillInvalidId[1](org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification)
>   Time elapsed: 0.009 sec  <<< ERROR!
> com.sun.jersey.test.framework.spi.container.TestContainerException: 
> java.net.BindException: Address already in use
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:433)
>   at sun.nio.ch.Net.bind(Net.java:425)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:413)
>   at 
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:384)
>   at 
> org.glassfish.grizzly.nio.transport.TCPNIOTransport.bind(TCPNIOTransport.java:375)
>   at 
> org.glassfish.grizzly.http.server.NetworkListener.start(NetworkListener.java:549)
>   at 
> org.glassfish.grizzly.http.server.HttpServer.start(HttpServer.java:255)
>   at 
> com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:326)
>   at 
> com.sun.jersey.api.container.grizzly2.GrizzlyServerFactory.createHttpServer(GrizzlyServerFactory.java:343)
>   at 
> com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.instantiateGrizzlyWebServer(GrizzlyWebTestContainerFactory.java:219)
>   at 
> com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.(GrizzlyWebTestContainerFactory.java:129)
>   at 
> com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory$GrizzlyWebTestContainer.(GrizzlyWebTestContainerFactory.java:86)
>   at 
> com.sun.jersey.test.framework.spi.container.grizzly2.web.GrizzlyWebTestContainerFactory.create(GrizzlyWebTestContainerFactory.java:79)
>   at 
> com.sun.jersey.test.framework.JerseyTest.getContainer(JerseyTest.java:342)
>   at com.sun.jersey.test.framework.JerseyTest.(JerseyTest.java:217)
>   at 
> org.apache.hadoop.yarn.webapp.JerseyTestBase.(JerseyTestBase.java:30)
>   at 
> org.apache.hadoop.yarn.server.resourcemanager.webapp.TestRMWebServicesAppsModification.(TestRMWebServicesAppsModification.java:277)
> {noformat}



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

-
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org