[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2018-03-12 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-1860:
--


Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch




> Oozie job mapper launch fails due to null value returned from action file
> -
>
> Key: OOZIE-1860
> URL: https://issues.apache.org/jira/browse/OOZIE-1860
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Osadchiy Artem
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-1860.patch, action.log, oozie.log
>
>
> Certain oozie workflows fail at launch mapper stage when the id retrieved 
> from the recovery action file returns a null value.
> Logs attached below



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2018-03-12 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-1860:
--

PreCommit-OOZIE-Build started


> Oozie job mapper launch fails due to null value returned from action file
> -
>
> Key: OOZIE-1860
> URL: https://issues.apache.org/jira/browse/OOZIE-1860
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Osadchiy Artem
>Priority: Major
> Fix For: trunk
>
> Attachments: OOZIE-1860.patch, action.log, oozie.log
>
>
> Certain oozie workflows fail at launch mapper stage when the id retrieved 
> from the recovery action file returns a null value.
> Logs attached below



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2016-07-27 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:red}-1{color} Patch failed to apply to head of branch



> Oozie job mapper launch fails due to null value returned from action file
> -
>
> Key: OOZIE-1860
> URL: https://issues.apache.org/jira/browse/OOZIE-1860
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Osadchiy Artem
> Fix For: trunk
>
> Attachments: OOZIE-1860.patch, action.log, oozie.log
>
>
> Certain oozie workflows fail at launch mapper stage when the id retrieved 
> from the recovery action file returns a null value.
> Logs attached below



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

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2015-12-15 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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: 1706
.Tests failed: 8
.Tests errors: 2

.The patch failed the following testcases:

.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)
.  testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.  testSamplers(org.apache.oozie.util.TestMetricsInstrumentation)
.  testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
.  
testCoordChangeConcurrency(org.apache.oozie.command.coord.TestCoordChangeXCommand)

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

> Oozie job mapper launch fails due to null value returned from action file
> -
>
> Key: OOZIE-1860
> URL: https://issues.apache.org/jira/browse/OOZIE-1860
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.1
>Reporter: Osadchiy Artem
> Fix For: trunk
>
> Attachments: OOZIE-1860.patch, action.log, oozie.log
>
>
> Certain oozie workflows fail at launch mapper stage when the id retrieved 
> from the recovery action file returns a null value.
> Logs attached below



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

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-08-25 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14110110#comment-14110110
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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} - patch does not compile, cannot run 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/1690/

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-08-22 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14107553#comment-14107553
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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: 1512
.Tests failed: 5
.Tests errors: 2

.The patch failed the following testcases:

.  testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.  testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.  testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.  testPig_withNullExternalID(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/1604/

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-08-22 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14107701#comment-14107701
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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: 1512
.Tests failed: 2
.Tests errors: 0

.The patch failed the following testcases:

.  
testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
.  
testConcurrencyReachedAndChooseNextEligible(org.apache.oozie.service.TestCallableQueueService)

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

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-08-03 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084018#comment-14084018
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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:green}+1 TESTS{color}
.Tests run: 1509
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


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

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

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-06-01 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14014925#comment-14014925
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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: 1463
.Tests failed: 3
.Tests errors: 2

.The patch failed the following testcases:

.  
testBundleEngineChange(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
.  
testBundleEngineKill(org.apache.oozie.servlet.TestV1JobServletBundleEngine)
.  
testActionInputCheckLatestActionCreationTime(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)

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

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-06-01 Thread Mona Chitnis (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14015094#comment-14015094
 ] 

Mona Chitnis commented on OOZIE-1860:
-

Are you seeing this error only in the case of sub-workflows?

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-05-30 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013413#comment-14013413
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+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:green}+1{color} the patch does not introduce any 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 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} - patch does not compile, cannot run 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/1276/

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (OOZIE-1860) Oozie job mapper launch fails due to null value returned from action file

2014-05-29 Thread Hadoop QA (JIRA) 

[ 
https://issues.apache.org/jira/browse/OOZIE-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14012494#comment-14012494
 ] 

Hadoop QA commented on OOZIE-1860:
--

Testing JIRA OOZIE-1860

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 90 line(s) with tabs
.{color:green}+1{color} the patch does not introduce any 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 1 testcase(s)
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 1 new RAT warning(s)
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{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} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails 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/1271/

 Oozie job mapper launch fails due to null value returned from action file
 -

 Key: OOZIE-1860
 URL: https://issues.apache.org/jira/browse/OOZIE-1860
 Project: Oozie
  Issue Type: Bug
Affects Versions: 4.0.1
Reporter: Osadchiy Artem
 Fix For: trunk

 Attachments: OOZIE-1860.patch, action.log, oozie.log


 Certain oozie workflows fail at launch mapper stage when the id retrieved 
 from the recovery action file returns a null value.
 Logs attached below



--
This message was sent by Atlassian JIRA
(v6.2#6252)