You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Chris Douglas (JIRA)" <ji...@apache.org> on 2008/07/09 20:13:31 UTC

[jira] Commented: (HADOOP-3725) TestMiniMRMapRedDebugScript loses exception details

    [ https://issues.apache.org/jira/browse/HADOOP-3725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12612212#action_12612212 ] 

Chris Douglas commented on HADOOP-3725:
---------------------------------------

+1, assuming Hudson doesn't object

> TestMiniMRMapRedDebugScript loses exception details
> ---------------------------------------------------
>
>                 Key: HADOOP-3725
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3725
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 0.19.0
>            Reporter: Steve Loughran
>            Priority: Minor
>         Attachments: hadoop-3725.patch
>
>
> The test class org.apache.hadoop.mapred.TestMiniMRMapRedDebugScript catches and prints exception details then calls fail(), rather than relaying the exception up to the calling test framework. this make the full stack trace harder to obtain. It could be a relic of the class having its own main() entry point.
> trivial to fix: add Exception to the test signature, move the catch/print into the main() method for that entry point

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.