ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11638) Configs: Different values in warnings tooltip when config is in raw mode.
Date Sun, 07 Jun 2015 22:27:04 GMT

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

Hadoop QA commented on AMBARI-11638:
------------------------------------

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

This message is automatically generated.

> Configs: Different values in warnings tooltip when config is in raw mode.
> -------------------------------------------------------------------------
>
>                 Key: AMBARI-11638
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11638
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Richard Zang
>            Assignee: Richard Zang
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11638.patch, AMBARI-11638_fixUT.patch
>
>
> STR:
> * Install cluster with Yarn
> * Navigate to MapReduce 2 configs
> * find *mapreduce.map.memory.mb* property and switch to raw mode
> * set value that is greater than maximum
> * hover mouse on label to check warn message
> * Value displayed in *megabytes* but unit is *GB*
> * Don't change the value and leave focus on input
> * Warning icon appears
> * hover mouse on label to check warn message
> * Value is converted to *GB*



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

Mime
View raw message