[
https://issues.apache.org/jira/browse/AMBARI-8361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215719#comment-14215719
]
Hadoop QA commented on AMBARI-8361:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12682055/AMBARI-8361.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/672//console
This message is automatically generated.
> Configs: UI breaks during particular flow
> -----------------------------------------
>
> Key: AMBARI-8361
> URL: https://issues.apache.org/jira/browse/AMBARI-8361
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8361.patch, broken-versions.tiff
>
>
> Configs UI breaks with the following flow:
> 1) go to tez
> 2) edit tez.am.resource.memory.mb and make 1
> 3) click save
> 4) that prompts the warning that this is not a recommended value
> 5) click cancel
> 6) browse to pig
> 7) you are prompted you have unsaved changes, click discard
> 9) Pig configs ui ends up broken
> have to browse away and come back for it to straighten out. See attached for
> example of broken-ness
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
