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

Hadoop QA commented on AMBARI-18416:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12829199/AMBARI-18416.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 6 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/8697//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/8697//console

This message is automatically generated.

> 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