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

Hadoop QA commented on OOZIE-2440:
----------------------------------

Testing JIRA OOZIE-2440

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:red}-1{color} the patch contains 1 line(s) with trailing spaces
.    {color:red}-1{color} the patch contains 1 line(s) longer than 132 
characters
.    {color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1790
.    Tests failed: 9
.    Tests errors: 2

.    The patch failed the following testcases:

.      testSingleRecord(org.apache.oozie.servlet.TestBulkMonitorWebServiceAPI)
.      
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommandNonUTC)
.      
testBundleStatusTransitWithLock(org.apache.oozie.service.TestStatusTransitService)
.      
testActionKillCommandDate(org.apache.oozie.command.coord.TestCoordActionsKillXCommand)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.      testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.      testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.      testMain(org.apache.oozie.action.hadoop.TestHiveMain)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3044/

> Exponential re-try policy for workflow action
> ---------------------------------------------
>
>                 Key: OOZIE-2440
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2440
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Satish Subhashrao Saley
>            Assignee: Satish Subhashrao Saley
>            Priority: Minor
>         Attachments: OOZIE-2440-2.patch, OOZIE-2440-3.patch, 
> OOZIE-2440-4.patch, OOZIE-2440-5.patch
>
>
> Currently the user can mention retry interval and maximum number of retries. 
> We will add another element in action tag through which the user can mention 
> policy for the retry. Policy could be exponential or periodic. Periodic will 
> be the default as it is the current policy.



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

Reply via email to