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

Hadoop QA commented on AMBARI-19240:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12843919/AMBARI-19240.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 1 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/9730//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9730//console

This message is automatically generated.

> Ambari UI should use "hosts_with_failures" from "host_resolution_check" in 
> host check
> -------------------------------------------------------------------------------------
>
>                 Key: AMBARI-19240
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19240
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19240.patch, AMBARI-19240_branch-2.5.patch
>
>
> Earlier UI parsed "failures" property value to get hosts which were failed. 
> But in perf clusters "failures" is very big (more than 300 MB), so we decided 
> to add one more property which contains only hostnames which failed.



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

Reply via email to