issue_comments: 572144220
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/pull/3667#issuecomment-572144220 | https://api.github.com/repos/pydata/xarray/issues/3667 | 572144220 | MDEyOklzc3VlQ29tbWVudDU3MjE0NDIyMA== | 14808389 | 2020-01-08T16:19:25Z | 2020-01-15T00:24:03Z | MEMBER | We use the upstream-dev check as a early warning system for changes in the unreleased versions of xarray's dependencies. It being the only failure usually means upstream (I guess pandas in this case) changed something, breaking some of xarray's tests. Since this also happens in other PRs and is completely unrelated (I think we don't run doctest in CI), I'd say you can safely ignore the failure. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
546451185 |