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

Hudson commented on AMBARI-18416:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #55 (See 
[https://builds.apache.org/job/Ambari-branch-2.5/55/])
AMBARI-18416. Optimize stack manager initialization for Ambari Server 
(aonishuk: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=07a3f950a510cc431ace458bde063d88175a4f94])
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ClusterStackVersionResourceProviderTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerTest.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/state/UpgradeHelperTest.java
* (edit) 
ambari-server/src/main/java/org/apache/ambari/server/stack/StackManager.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* (add) 
ambari-server/src/test/java/org/apache/ambari/server/stack/StackManagerMock.java
* (edit) 
ambari-server/src/test/java/org/apache/ambari/server/orm/InMemoryDefaultTestModule.java


> Optimize stack manager initialization for Ambari Server Unit Tests
> ------------------------------------------------------------------
>
>                 Key: AMBARI-18416
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18416
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18416.patch
>
>
> Currently the stack dirs scanning occurs on every test module creation. It
> takes about 0.5 second for each test method.



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

Reply via email to