[
https://issues.apache.org/jira/browse/AMBARI-12117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599266#comment-14599266
]
Hadoop QA commented on AMBARI-12117:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12741579/AMBARI-12117.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/3251//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3251//console
This message is automatically generated.
> Heatmaps: Maximum input is reseting every 15 seconds
> ----------------------------------------------------
>
> Key: AMBARI-12117
> URL: https://issues.apache.org/jira/browse/AMBARI-12117
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12117.patch
>
>
> STR:
> 1. Go to Heatmaps.
> 2. Change Maximum value for selected metric.
> Every 15 sec. Maximum value is updated to default, ignoring user input, so
> user unable to work with heatmaps as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
