You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/11/02 20:41:58 UTC

[jira] [Created] (TEZ-3508) TestTaskScheduler cleanup

Jason Lowe created TEZ-3508:
-------------------------------

             Summary: TestTaskScheduler cleanup
                 Key: TEZ-3508
                 URL: https://issues.apache.org/jira/browse/TEZ-3508
             Project: Apache Tez
          Issue Type: Test
            Reporter: Jason Lowe
            Assignee: Jason Lowe


TestTaskScheduler is very fragile, since it builds mocks of the AMRM client that is tied very specifically to the particulars of the way the YarnTaskScheduler is coded.  Any variance in that often leads to test failures because the mocks no longer accurately reflect what the real AMRM client does.

It would be much simpler and more robust to leverage the AMRMClientForTest and AMRMAsyncClientForTest classes in TestTaskSchedulerHelpers rather than maintain fragile mocks attempting to emulate the behaviors of those classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)