issue_comments: 346670364

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-346670364 https://api.github.com/repos/pydata/xarray/issues/1738 346670364 MDEyOklzc3VlQ29tbWVudDM0NjY3MDM2NA== 306380 2017-11-23T17:22:26Z 2017-11-23T17:22:26Z MEMBER

It might be useful in the future to change one of XArray's test builds to be against git-master rather than latest release. This would help us to identify issues like this closer to when they occurred.

On Thu, Nov 23, 2017 at 12:20 PM, Stephan Hoyer notifications@github.com wrote:

Comparing a failed https://ci.appveyor.com/project/shoyer/xray/build/1.0.3015 build to the last successful https://ci.appveyor.com/project/shoyer/xray/build/1.0.3012 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 (only setup.py and documentation changes).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/1738#issuecomment-346670059, or mute the thread https://github.com/notifications/unsubscribe-auth/AASszEI5Wou1G91aMSsN7lCuovp2cDSAks5s5alwgaJpZM4QoKTw . 

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