Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use cluster.scheduler_info rather than cluster.scheduler #73

Merged
merged 5 commits into from
Aug 1, 2019

Commits on Jul 28, 2019

  1. Use cluster.scheduler_info rather than cluster.scheduler

    Supercedes dask#72
    
    This depends on dask/distributed#2902 , which
    adds a `Cluster.scheduler_info` attribute to clusters which holds
    necessary scheduler information.  We prefer this over querying a
    Scheduler object directly in case that scheduler is not local, as in
    increasingly becoming the case.
    mrocklin committed Jul 28, 2019
    Configuration menu
    Copy the full SHA
    cc5437d View commit details
    Browse the repository at this point in the history

Commits on Jul 31, 2019

  1. Configuration menu
    Copy the full SHA
    3fa7454 View commit details
    Browse the repository at this point in the history
  2. Fixup config in tests

    Otherwise we didn't seem to be getting the baseline config, which was
    causing errors.
    mrocklin committed Jul 31, 2019
    Configuration menu
    Copy the full SHA
    3ae2bcc View commit details
    Browse the repository at this point in the history

Commits on Aug 1, 2019

  1. use dask=2.1 in CI

    mrocklin committed Aug 1, 2019
    Configuration menu
    Copy the full SHA
    3ab9d8f View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    22be0ea View commit details
    Browse the repository at this point in the history