[
https://issues.apache.org/jira/browse/OOZIE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172374#comment-14172374
]
Hadoop QA commented on OOZIE-2001:
----------------------------------
Testing JIRA OOZIE-2001
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:red}-1{color} the patch contains 4 line(s) with tabs
. {color:green}+1{color} the patch does not introduce any 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 1 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: 1541
. Tests failed: 0
. Tests errors: 8
. The patch failed the following testcases:
.
{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/2044/
> Workflow re-runs doesn't update coord action status
> ---------------------------------------------------
>
> Key: OOZIE-2001
> URL: https://issues.apache.org/jira/browse/OOZIE-2001
> Project: Oozie
> Issue Type: Bug
> Reporter: Shwetha G S
> Assignee: Jaydeep Vishwakarma
> Attachments: OOZIE-2001-v1.patch, OOZIE-2001-v2.patch,
> OOZIE-2001.patch, rerun-0.patch
>
>
> When a workflow is re-run, the corresponding coord action status is not
> updated and coord action stays in killed state. This gives wrong impression
> that coord action is not running which is not the case
> SignalXCommand:
> {code}
> // Changing to synchronous call from asynchronous queuing to prevent
> // undue delay from between end of previous and start of next action
> if (wfJob.getStatus() != WorkflowJob.Status.RUNNING
> && wfJob.getStatus() != WorkflowJob.Status.SUSPENDED) {
> // only for asynchronous actions, parent coord action's external
> id will
> // persisted and following update will succeed.
> updateParentIfNecessary(wfJob);
> new WfEndXCommand(wfJob).call(); // To delete the WF temp dir
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
