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

Hadoop QA commented on AMBARI-8684:
-----------------------------------

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

This message is automatically generated.

> RU progress popup: stops updating on poll
> -----------------------------------------
>
>                 Key: AMBARI-8684
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8684
>             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-8684.patch
>
>
> When polling for upgrade progress, the upgrade data stops updating.
> I'm seeing this error on the JS console:
> DEPRECATION: Something you did caused a view to re-render after it rendered 
> but before it was inserted into the DOM. Because this is avoidable and the 
> cause of significant performance issues in applications, this behavior is 
> deprecated. If you want to use the debugger to find out what caused this, you 
> can set ENV.RAISE_ON_DEPRECATION to true.



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

Reply via email to