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

Hadoop QA commented on AMBARI-15070:
------------------------------------

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

This message is automatically generated.

> Graph scale behaviour is incorrect if time range is switched before graph 
> data API call is complete
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-15070
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15070
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.2
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15070_222.patch, AMBARI-15070_trunk.patch
>
>
> *STR*
> # Switch metrics time range from 'Last 1 hour' to 'Last 1 year' (for example, 
> on Dashboard; data for 1 year should be available).
> # While metrics API call is pending, switch time range back to 1 hour (can be 
> reproduced if connection rate is low or server is highly loaded so that 
> requests are being processed slowly).
> *Result*
> After request with data for last year is complete, it's displayed on the 
> graph, but the scale is rendered with an accuracy to 1 hour which makes graph 
> unusable 



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

Reply via email to