[
https://issues.apache.org/jira/browse/AMBARI-20603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945291#comment-15945291
]
Hadoop QA commented on AMBARI-20603:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12860861/AMBARI-20603.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/11213//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/11213//console
This message is automatically generated.
> Hadoop QA compiles trunk twice
> ------------------------------
>
> Key: AMBARI-20603
> URL: https://issues.apache.org/jira/browse/AMBARI-20603
> Project: Ambari
> Issue Type: Bug
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Fix For: 3.0.0
>
> Attachments: AMBARI-20603.patch
>
>
> * The "Pre-build trunk" step of the [Ambari-trunk-test-patch
> job|https://builds.apache.org/job/Ambari-trunk-test-patch/] compiles Ambari
> twice, unnecessarily increasing elapsed time by 5-6 minutes.
> * RAT check is executed twice: in the "javac warnings" and the "release audit
> warnings" steps. The problem is that the report with the list of any files
> that failed the RAT check is made available only in the second step, which is
> not run if the check fails in the first step. The only way to find offenders
> is to run the check locally.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
