[
https://issues.apache.org/jira/browse/AMBARI-9956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353450#comment-14353450
]
Hadoop QA commented on AMBARI-9956:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12703467/AMBARI-9956.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 javac{color}. The applied patch does not increase the
total number of javac compiler 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/Ambari-trunk-test-patch/1970//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1970//console
This message is automatically generated.
> RU: display repository name in versionbox
> -----------------------------------------
>
> Key: AMBARI-9956
> URL: https://issues.apache.org/jira/browse/AMBARI-9956
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9956.patch, AMBARI-9956_1.patch
>
>
> It is hard to find this information and the user needs this in the case of
> manual upgrade. It's a challenge to doc how to find this.
> The info is available via the api and is coming back to UI already.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
