[
https://issues.apache.org/jira/browse/AMBARI-14564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163614#comment-15163614
]
Hudson commented on AMBARI-14564:
---------------------------------
ABORTED: Integrated in Ambari-trunk-Commit #4382 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4382/])
AMBARI-14564. Removed -Ignore from test cases, removed -Noncacheable (ncole:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7e306c555ba9a73b54c8200340789547e8182ec5])
*
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDispatchDAOTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/RequestDAOTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/orm/dao/AlertDefinitionDAOTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/AlertTargetEntity.java
> 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)
