conda setup fails on dependency check when adding tools

[ml31415]

We had a github workflow for building conda packages, that was was setup to run nightly and did so without problems for quite some time. Lately setup-miniconda@v2 fails on the step Adding tools to 'base' env... with a ton of dependency errors, that aren't any dependency of the package, but of - I suppose - conda.

This is the lengthy error log:

https://github.com/ml31415/numpy-groupies/actions/runs/4527421235/jobs/7973256139#step:5:263

Workflow file:

https://github.com/ml31415/numpy-groupies/blob/master/.github/workflows/ci.yaml

I tried to get rid of any caching, but that didn't seem to be the issue. Any help with that would be greatly appreciated!

[goanpeca]

Hi @ml31415, thanks for the report and sorry for the issues. I will take a look. In the meantime, does using any specific version tag of the 2.x series work?

v2, always points to the latest one (as per github recommendations)

@jaimergp, any thoughts on the conflict resolution errors in the reported file?

Cheers!

[ml31415]

Thanks for the quick response, @goanpeca ! @dcherian was so kind, to fix our workflow using micromamba for now. I hope this issue report is still useful and updated the link above to a commit that has the described issue.

Btw. the first time that this issue occurred, was on January 12th. Maybe this helps, to narrow down the cause.

[oneebhkhan]

I am facing this exact issue. My CI setup has been working well for weeks. However on Friday 20th July my build failed because of dependency issues. And since then this workflow is failing all the time. There has been no change to either the environment.yml file or the workflow file. And I am unable to make sense of how to resolve this.

[jaimergp]

Can you share a link to the logs @oneebhkhan? Thanks 🙏 !

[oneebhkhan]

Logs:
https://pipelines.actions.githubusercontent.com/serviceHosts/7592902d-5cd5-45cb-a8f1-94ca90672c93/_apis/pipelines/1/runs/208/signedlogcontent/2?urlExpires=2023-07-24T12%3A34%3A26.1876502Z&urlSigningMethod=HMACV1&urlSignature=Zfv6%2BznQqZnVvS8NZVvNTtd57r38xdkQi7feO4NrmdQ%3D

[jaimergp]

I need a link to the PR or CI run, not the direct logs (those expire after a bit, so it doesn't work right now).

[oneebhkhan]

The repo is in a private organization on Github so I won't be able to share that.
But I've attached the logs here:
conda github action logs.zip

[jaimergp]

It looks like you are asking the solver to change from defaults to conda-forge, which is an operation that is exposed to a good deal of "friction". It'd be easier to start with Mambaforge as your base install, and then install whatever you need on top (see Example 10). Let me know if that helps.

[oneebhkhan]

It looks like this works! Thank you @jaimergp for getting back to me so quickly! Really appreciate it.