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

Hadoop QA commented on AMBARI-8965:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12689661/AMBARI-8965.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/1134//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/1134//console

This message is automatically generated.

> Upgrade Progress: Show "Ignore and Continue" and "Retry" buttons based on the 
> API response
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8965
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8965
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8965.patch
>
>
> # Allow Retry - mark a stage (upgrade item) to allow any failed task to be 
> retried.  This means that if a failure occurs during the execution of the 
> task then the stage & task will transition to HOLDING_FAILED.  Once in the 
> HOLDING_FAILED state, the stage can be pushed to PENDING (retry) or FAILED.  
> Transitioning the stage to FAILED will cause the remaining tasks in that 
> stage to be ABORTED.  It never makes sense to allow the remaining tasks of a 
> stage to continue executing after the stage has been accepted as FAILED.  
> However, the remaining stages of the upgrade request may be allowed execute...
> # Skippable - mark a stage to allow it to be skipped in the event of a 
> failure so that the remaining stages may still execute.  This means that when 
> a stage state is set to FAILED, it will not trigger the remaining stages of 
> the request to abort.



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

Reply via email to