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

Hadoop QA commented on AMBARI-20903:
------------------------------------

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

    {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 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

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

    {color:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  org.apache.ambari.server.stack.StackManagerTest

Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/11561//console

This message is automatically generated.

> RepoVersion parsing error should be more specific
> -------------------------------------------------
>
>                 Key: AMBARI-20903
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20903
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: AMBARI-20903.patch
>
>
> This is a minor JIRA on updating an error message in case the repoinfo.xml 
> misses any of the three required fields - repo_name, repo_id, and base url.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to