[
https://issues.apache.org/jira/browse/AMBARI-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086215#comment-15086215
]
Hadoop QA commented on AMBARI-14564:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12780753/AMBARI-14564.v1.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 3 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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4795//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4795//console
This message is automatically generated.
> Fix unit test failures
> -----------------------
>
> Key: AMBARI-14564
> URL: https://issues.apache.org/jira/browse/AMBARI-14564
> Project: Ambari
> Issue Type: Bug
> Components: alerts, ambari-server
> Affects Versions: 2.2.0
> Reporter: Laszlo Puskas
> Assignee: Laszlo Puskas
> Fix For: 2.2.1
>
> Attachments: AMBARI-14564.v1.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Some unit tests started to fail after a previously introduced change.
> Context:
> - subsequently changing alert targets (changing alert groups attached to
> alert targets) resulted in ConcurrentModificationException
> - changing the code that updates alert groups fixed the CME, however another
> issue arose: after subsequently changing alert targets, at a given point
> changes were not reflected after save
> - excluding the relationship between alert targets and alert groups from
> caching solved the problem
> This solution apparently caused a regression in the cluster deletion process.
> This issue is about removing @Ignore annotations and providing a good
> implementation for the causing issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
