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

Hadoop QA commented on AMBARI-18879:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12838850/AMBARI-18879.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:red}-1 core tests{color}.  The patch failed these unit tests in 
ambari-server:

                  
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9266//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9266//console

This message is automatically generated.

> Remaining components should be stack_select'ed for completeness
> ---------------------------------------------------------------
>
>                 Key: AMBARI-18879
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18879
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-18879.patch
>
>
> With HOST_ORDERED orchestration (much like RU today), there is the 
> possibility of mixed components after upgrade.  Orchestration should add a 
> task that will stack_select ({{hdp-select}} for HDP) after other tasks have 
> completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to