GitHub user kayousterhout opened a pull request:

    https://github.com/apache/spark/pull/3967

    [SPARK-1143] Separate pool tests into their own suite.

    The current TaskSchedulerImplSuite includes some tests that are
    actually for the TaskSchedulerImpl, but the remainder of the tests avoid 
using
    the TaskSchedulerImpl entirely, and actually test the pool and scheduling
    algorithm mechanisms. This commit separates the pool/scheduling algorithm
    tests into their own suite, and also simplifies those tests.
    
    The pull request replaces #339.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kayousterhout/spark-1 SPARK-1143

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/3967.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3967
    
----
commit 8a898c45d923f6106548cff7ab869ae757ff4159
Author: Kay Ousterhout <[email protected]>
Date:   2015-01-06T21:47:11Z

    [SPARK-1143] Separate pool tests into their own suite.
    
    The current TaskSchedulerImplSuite includes some tests that are
    actually for the TaskSchedulerImpl, but many of the tests avoid using
    the TaskSchedulerImpl entirely, and actually test the pool and scheduling
    algorithm mechanisms. This commit separates the pool/scheduling algorithm
    tests into their own suite, simplifies those tests, and attempts to
    more helpfully comment the fair scheduler test.
    
    The pull request replaces #339.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to