[jira] Commented: (MAPREDUCE-2271) TestSetupTaskScheduling failing in trunk

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on MAPREDUCE-2271:
----------------------------------------

Sorry if I'm being dense, but I don't quite follow the logic of this test. Could you help me understand what's supposed to be going on here?

It seems createJob() already makes the two cleanup tasks with status as FAILED_UNCLEAN from that tracker. Is the change in MAPREDUCE-2207 only such that the cleanup-tasks won't be rescheduled in response to the same heartbeat that marked them failed? So in this test we get them scheduled because it's a new heartbeat with no task statuses, even though it previously had failed on that tracker?

> TestSetupTaskScheduling failing in trunk
> ----------------------------------------
>
>                 Key: MAPREDUCE-2271
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2271
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Priority: Blocker
>         Attachments: 2271-1.diff
>
>
> This test case is failing in trunk after the commit of MAPREDUCE-2207

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