[
https://issues.apache.org/jira/browse/AMBARI-15057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15148818#comment-15148818
]
Hadoop QA commented on AMBARI-15057:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12788047/AMBARI-15057.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 1 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/5388//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5388//console
This message is automatically generated.
> Oozie untar and prepare-war should be only done exclusively in preupload.py
> ---------------------------------------------------------------------------
>
> Key: AMBARI-15057
> URL: https://issues.apache.org/jira/browse/AMBARI-15057
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15057.patch
>
>
> This critically hits deploy times on users cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)