Hadoop QA commented on YARN-1900:

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

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

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

This message is automatically generated.

> yarn.log.server.url needs to specify an http:// prefix
> ------------------------------------------------------
>                 Key: YARN-1900
>                 URL: https://issues.apache.org/jira/browse/YARN-1900
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.2.0, 2.3.0, 2.4.0
>            Reporter: Robert On
>            Assignee: Tsuyoshi OZAWA
>            Priority: Minor
>         Attachments: YARN-1900.1.patch
> If yarn.log.server.url in yarn-site.xml is specified with an http:// prefix 
> and log-aggregation is turned on, the meta-refresh redirect for non-mapreduce 
> jobs will append the url to the end of the current url rather than replace 
> the entire url with the yarn.log.server.url.  This results in a broken 
> redirect for FINISHED yarn jobs.  

This message was sent by Atlassian JIRA

Reply via email to