[ 
https://issues.apache.org/jira/browse/TEZ-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14295016#comment-14295016
 ] 

Hadoop QA commented on TEZ-1987:
--------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12694950/TEZ-1987.1.patch
  against master revision 1e680a5.

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

This message is automatically generated.

> Tez UI non-standalone mode uses invalid protocol
> ------------------------------------------------
>
>                 Key: TEZ-1987
>                 URL: https://issues.apache.org/jira/browse/TEZ-1987
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Gopal V
>            Assignee: Sreenath Somarajapuram
>            Priority: Trivial
>         Attachments: TEZ-1987.1.patch
>
>
> When Tez UI is used in non-standalone mode, it accesses 
> "http//<hostname>:8188" instead of the correct protocol setting.
> That is parsed as a relative URL than as an absolute host:port URI.



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

Reply via email to