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

Hadoop QA commented on OOZIE-1810:
----------------------------------

Testing JIRA OOZIE-1810

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 2 line(s) with trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:green}+1{color} the patch does adds/modifies 2 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: 1559
.    Tests failed: 1
.    Tests errors: 0

.    The patch failed the following testcases:

.      
testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker)

{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/2112/

> Workflow cannot get into Failed state when kill control node cannot resolve 
> variable in message 
> ------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1810
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1810
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Bing Jiang
>            Assignee: Azrael
>             Fix For: trunk
>
>         Attachments: OOZIE-1810.2.patch, OOZIE-1810.patch
>
>
> ====workflow.xml======
> <workflow-app name='test-kill-wf' xmlns="uri:oozie:workflow:0.3">
> <start to='fail'/>
> <kill name="fail">
> <message>${TryError} error 
> message[${wf:errorMessage(wf:lastErrorNode())}]</message>
> </kill>
> <end name="end"/>
> </workflow-app>
> There is no definition about ${TryError} in job.properties.
> Workflow job are stuck at RUNNING state, and it is always trying to resolve 
> the variable [TryError] in kill action's message.
> ======Exception from oozie log ========
> ACTION[****-*************-oozie-wrkf-W@fail] XException, 
> org.apache.oozie.command.CommandException: E0729: Kill node message [fail]
>       at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:292)
>       at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:66)
>       at org.apache.oozie.command.XCommand.call(XCommand.java:280)
>       at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>       at java.lang.Thread.run(Thread.java:722)
> Caused by: javax.servlet.jsp.el.ELException: variable [TryError] cannot be 
> resolved
>       at 
> org.apache.oozie.util.ELEvaluator$Context.resolveVariable(ELEvaluator.java:106)
>       at org.apache.commons.el.NamedValue.evaluate(NamedValue.java:124)
>       at 
> org.apache.commons.el.ExpressionString.evaluate(ExpressionString.java:114)
>       at 
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:274)
>       at 
> org.apache.commons.el.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:190)
>       at org.apache.oozie.util.ELEvaluator.evaluate(ELEvaluator.java:203)
>       at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:277)
>       ... 6 more
> ===================
> when it runs into  the resolve error upon control nodes' message, oozie 
> action should enter into Failed state as soon as possible.



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

Reply via email to