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

Hadoop QA commented on AMBARI-15060:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12788593/AMBARI-15060-trunk-v2.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 2 new 
or modified test files.

    {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 
ambari-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5470//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5470//console

This message is automatically generated.

> Ambari should show no. of HAWQ segments live on main dashboard
> --------------------------------------------------------------
>
>                 Key: AMBARI-15060
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15060
>             Project: Ambari
>          Issue Type: Story
>          Components: ambari-web
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.2.2
>
>         Attachments: AMBARI-15060-branch-2.2-orig.patch, 
> AMBARI-15060-branch-2.2-v1.patch, AMBARI-15060-branch-2.2-v2.patch, 
> AMBARI-15060-trunk-orig.patch, AMBARI-15060-trunk-v1.patch, 
> AMBARI-15060-trunk-v2.patch, green.png, orange.png, red.png
>
>
> The no. of HAWQ segments alive should be displayed as a widget on Ambari's 
> main dashboard.



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

Reply via email to