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

Hadoop QA commented on AMBARI-20054:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12853133/AMBARI-20054.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 5 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.checks.DatabaseConsistencyCheckHelperTest
                  org.apache.ambari.server.agent.TestHeartbeatHandler
                  
org.apache.ambari.server.controller.metrics.RestMetricsPropertyProviderTest

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

This message is automatically generated.

> Remove Entities Associated With clusterconfigmapping
> ----------------------------------------------------
>
>                 Key: AMBARI-20054
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20054
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: trunk
>
>         Attachments: AMBARI-20054.patch
>
>
> - Remove the {{clusterconfigmapping}} table, which has redundant columns and 
> causes nothing but headaches when it becomes out of sync with 
> {{clusterconfig}}
> - Change {{clusterconfig}} to track which configuration is selected and when 
> the last time it was selected was



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to