[
https://issues.apache.org/jira/browse/MAPREDUCE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750564#action_12750564
]
gary murry commented on MAPREDUCE-421:
--------------------------------------
Thanks for adding the extra info on your testing. As for the core and contrib
test failures, I agree that we have tests that fail for unrelated reason. But
it is good to link those failure to the jira, so that we can get momentum to
get them fixed too. It would be nice some day to have enough confidence in all
the tests that we can say a failure is most likely related to the code it is
testing. Thanks again.
> mapred pipes might return exit code 0 even when failing
> -------------------------------------------------------
>
> Key: MAPREDUCE-421
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-421
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: pipes
> Reporter: Christian Kunz
> Assignee: Christian Kunz
> Fix For: 0.20.1
>
> Attachments: MAPREDUCE-421.patch
>
>
> up to hadoop 0.18.3 org.apache.hadoop.mapred.JobShell ensured that 'hadoop
> jar' returns non-zero exit code when the job fails.
> This is no longer true after moving this to org.apache.hadoop.util.RunJar.
> Pipes jobs submitted through cli never returned proper exit code.
> The main methods in org.apache.hadoop.util.RunJar. and
> org.apache.hadoop.mapred.pipes.Submitter should be modified to return an exit
> code similar to how org.apache.hadoop.mapred.JobShell did it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
