[
https://issues.apache.org/jira/browse/AMBARI-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269257#comment-14269257
]
Hadoop QA commented on AMBARI-9040:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12690810/AMBARI-9040.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/1233//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1233//console
This message is automatically generated.
> Chrome being flooded with errors, unresponsive page
> ---------------------------------------------------
>
> Key: AMBARI-9040
> URL: https://issues.apache.org/jira/browse/AMBARI-9040
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9040.patch
>
>
> Currently testing out RU, but seeing many instances of a stack in the chrome
> console:
> {noformat}
> 2ember-latest.js:110 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.
> at Ember.View.states.inBuffer.rerender
> (http://localhost:8080/javascripts/vendor.js:15498:11)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://localhost:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.rerender
> (http://localhost:8080/javascripts/vendor.js:14177:17)
> at Ember.View.states.inBuffer.$
> (http://localhost:8080/javascripts/vendor.js:15491:10)
> at Ember.View.Ember.Object.extend.invokeForState
> (http://localhost:8080/javascripts/vendor.js:14134:17)
> at Ember.View.Ember.Object.extend.$
> (http://localhost:8080/javascripts/vendor.js:14353:17)
> at observer (http://localhost:8080/javascripts/vendor.js:20421:85)
> at invoke (http://localhost:8080/javascripts/vendor.js:5036:19)
> at Object.invokeOnceTimer
> (http://localhost:8080/javascripts/vendor.js:5463:23)
> {noformat}
> It happens constantly, eventually filling with about 50,000 instances before
> chrome says it's killing the page.
> This is a clean build from ambari-web, trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
