Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sun, 13 Mar 2016 02:36:33 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12949654.1457836461000.783.1457836593453@Atlassian.JIRA>
In-Reply-To: <JIRA.12949654.1457836461000@Atlassian.JIRA>
References: <JIRA.12949654.1457836461000@Atlassian.JIRA>
 <JIRA.12949654.1457836461781@arcas>
Subject: [jira] [Updated] (YARN-4805) Don't go through all schedulers in
 ParameterizedTestBase
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-4805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla updated YARN-4805:
-----------------------------------
    Attachment: yarn-4805-1.patch

> Don't go through all schedulers in ParameterizedTestBase
> --------------------------------------------------------
>
>                 Key: YARN-4805
>                 URL: https://issues.apache.org/jira/browse/YARN-4805
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: yarn-4805-1.patch
>
>
> ParameterizedSchedulerTestBase was created to make sure tests that were written with CapacityScheduler in mind don't fail when run against FairScheduler. Before this was introduced, tests would fail because FairScheduler requires an allocation file. 
> However, the tests that extend it take about 10 minutes per scheduler. So, instead of running against both schedulers, we could setup the scheduler appropriately so the tests pass against both schedulers. 


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