[
https://issues.apache.org/jira/browse/AMBARI-16220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325448#comment-15325448
]
Hadoop QA commented on AMBARI-16220:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12809486/AMBARI-16220.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 2 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:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.ServicePropertiesTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/7304//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7304//console
This message is automatically generated.
> No INSTALL commands
> -------------------
>
> Key: AMBARI-16220
> URL: https://issues.apache.org/jira/browse/AMBARI-16220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Reporter: Sebastian Toader
> Assignee: Sandor Magyari
> Fix For: 2.5.0
>
> Attachments: AMBARI-16220.patch
>
>
> In case packages.pre.installed=true is set in ambari.properties, Blueprint
> based deployments will not create INSTALL commands for service components.
> Normally START command should call configure, but we must ensure this is true
> for all used components. For client components INSTALL will be still
> generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
