[
https://issues.apache.org/jira/browse/AMBARI-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241242#comment-14241242
]
Hadoop QA commented on AMBARI-8633:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12686277/AMBARI-8633.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/875//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/875//console
This message is automatically generated.
> Dashboard > Config History tab does a "double load"
> ---------------------------------------------------
>
> Key: AMBARI-8633
> URL: https://issues.apache.org/jira/browse/AMBARI-8633
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8633.patch
>
>
> Go to Dashboard > Config History page. The table loads twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
