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

Hadoop QA commented on AMBARI-17340:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12812213/AMBARI-17340.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.controller.internal.ConfigGroupResourceProviderTest
                  org.apache.ambari.server.state.ServicePropertiesTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7456//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/7456//console

This message is automatically generated.

> Alert mapreduce_history_server_process fails after enabling SSL
> ---------------------------------------------------------------
>
>                 Key: AMBARI-17340
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17340
>             Project: Ambari
>          Issue Type: Bug
>          Components: alerts, ambari-upgrade
>    Affects Versions: 2.2.2
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17340.patch
>
>
> Remove mapreduce_history_server_process , it duplicates 
> mapreduce_history_server_webui



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

Reply via email to