issue_comments: 346670059

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/issues/1738#issuecomment-346670059 https://api.github.com/repos/pydata/xarray/issues/1738 346670059 MDEyOklzc3VlQ29tbWVudDM0NjY3MDA1OQ== 1217238 2017-11-23T17:20:46Z 2017-11-23T17:20:46Z MEMBER

Comparing a failed build to the last successful build on master, I find the following difference in the dependencies: ```

passed, just before the v0.10.0 release

ca-certificates 2017.7.27.1 0 conda-forge dask 0.15.4 py_0 conda-forge dask-core 0.15.4 py_0 conda-forge distributed 1.19.3 py27_0 conda-forge setuptools 36.6.0 py27_1 conda-forge

failed, at the v0.10.0 release

ca-certificates 2017.11.5 0 conda-forge dask 0.16.0 py_0 conda-forge dask-core 0.16.0 py_0 conda-forge distributed 1.20.0 py27_0 conda-forge setuptools 36.7.2 py27_0 conda-forge `` It looks like dask 0.16 or distributed 0.1.20 release is the most likely culprit. There were no Python changes to xarray in the v0.10.0 release commit (onlysetup.py` and documentation changes).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   276241193