[
https://issues.apache.org/jira/browse/OOZIE-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16578671#comment-16578671
]
Hadoop QA commented on OOZIE-3298:
----------------------------------
Testing JIRA OOZIE-3298
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:green}+1{color} the patch does not introduce any trailing spaces
. {color:red}-1{color} the patch contains 2 line(s) longer than 132
characters
. {color:green}+1{color} the patch adds/modifies 5 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 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warning(s)
. {color:red}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
error(s)
{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{color} There are no new bugs found in total.
{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: 2925
. Tests failed: 2
. Tests errors: 0
. The patch failed the following testcases:
testRerun(org.apache.oozie.action.hadoop.TestRerun)
testFailingMapReduceJobCausesOozieLauncherAMToFail(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
. Tests failing with errors:
. {color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
. For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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}
{color:red}. There is at least one warning, please check{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/751/
> OYA: external ID is not filled properly and failing MR job is treated as
> SUCCEEDED
> ----------------------------------------------------------------------------------
>
> Key: OOZIE-3298
> URL: https://issues.apache.org/jira/browse/OOZIE-3298
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: Peter Bacsko
> Assignee: Andras Piros
> Priority: Blocker
> Fix For: 5.1.0
>
> Attachments: OOZIE-3298.001.patch, OOZIE-3298.002.patch,
> OOZIE-3298.003.patch, OOZIE-3298.004.patch, OOZIE-3298.005.patch
>
>
> When a MapReduce action is launched from Oozie (OYA), we don't properly fill
> the external ID field. It gets populated with the YARN id of the LauncherAM,
> not with the id of the actual MR job. If the MR job is succesfully submitted
> then fails, it will be treated as a successfully executed action, which is
> very misleading and can potentially confuse Oozie users.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
