You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/09/19 13:19:21 UTC
[jira] [Commented] (AMBARI-18416) Optimize stack manager
initialization for Ambari Server Unit Tests
[ https://issues.apache.org/jira/browse/AMBARI-18416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503468#comment-15503468 ]
Hadoop QA commented on AMBARI-18416:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12829189/AMBARI-18416.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/8694//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)