issues: 755566566

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
755566566 MDU6SXNzdWU3NTU1NjY1NjY= 4643 mamba does not use strict channel priority (in our CI) 10194086 closed 0     0 2020-12-02T19:54:19Z 2020-12-05T00:30:11Z 2020-12-05T00:30:11Z MEMBER      

We use mamba in the new CI:

https://github.com/pydata/xarray/blob/7152b41fa80a56db0ce88b241fbe4092473cfcf0/.github/workflows/upstream-dev-ci.yaml#L39

I just tested it and it is awesomely fast! However, it does not enforce strict channel priority, so packages from main get mixed in (see e.g. https://github.com/pydata/xarray/runs/1487637678#step:5:112 & search for main) & we don't want that. So I'd suggest to do:

bash mamba env update --override-channels -c conda-forge -f ci/requirements/py38.yml

(note there is a --strict-channel-priority option in mamba but it still installed packages from main when I tested it)

cc @andersy005: mybe you could add this to #4604?

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/4643/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 13221727 issue

Links from other tables