[
https://issues.apache.org/jira/browse/AMBARI-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291023#comment-15291023
]
Hadoop QA commented on AMBARI-16767:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12804930/AMBARI-16767.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
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6894//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6894//console
This message is automatically generated.
> Persist UI console errors
> -------------------------
>
> Key: AMBARI-16767
> URL: https://issues.apache.org/jira/browse/AMBARI-16767
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-16767.patch
>
>
> We have a lot of situations when after page refresh or re login issue/console
> error is gone and there is no opportunity to track and understand the root
> source of the problem. The easiest way is to at least persist this error. So
> for example after CI tests we can login to cluster that has an issue and see
> all UI errors that it had.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
