Hadoop QA commented on YARN-2275:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

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

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

    {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 


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

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

This message is automatically generated.

> When log aggregation not enabled, message should point to NM HTTP port, not 
> IPC port 
> -------------------------------------------------------------------------------------
>                 Key: YARN-2275
>                 URL: https://issues.apache.org/jira/browse/YARN-2275
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: log-aggregation
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Ray Chiang
>         Attachments: MAPREDUCE5185-01.patch
> When I try to get a container's logs in the JHS without log aggregation 
> enabled, I get a message that looks like this:
> "Aggregation is not enabled. Try the nodemanager at sandy-ThinkPad-T530:33224"
> This could be a lot more helpful by actually pointing the URL that would show 
> the container logs on the NM.

This message was sent by Atlassian JIRA

Reply via email to