hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3489) Unit tests failing silently
Date Thu, 01 Dec 2011 08:09:42 GMT

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

Sharad Agarwal commented on MAPREDUCE-3489:
-------------------------------------------

Definately System.exit is not the right thing in a library. Sigh! I knew that when I wrote
that and intended to remove it. Couldn't get chance to get to it. 
I think we should get rid of it and instead have a error handling callback registered to Dispatcher.
                
> Unit tests failing silently
> ---------------------------
>
>                 Key: MAPREDUCE-3489
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3489
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Siddharth Seth
>            Priority: Critical
>
> If one of the dispatched events generates an exception - the dispatcher kills the JVM
via a System.exit. Unit tests end up not running - but they don't fail either.
> TestTaskAttempt is currently running like this.
> Previously - have seen TestRecovery and TestJobHistoryParsing do the same. Most of the
tests would need to be looked at.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message