Open jonashaag opened 1 year ago
We're also bumping into this, on a self-hosted runner, even with caching set to false. do you have any advice? (on linux)
We're also hitting this on a self-hosted runner (macOS ARM64). Caching is also not enabled. Since the clean-up fails, any subsequent job fails at the startup since the ~/micromamba
folder is already present.
An easy fix should be to use generate-run-shell: false
. I'll try to take a look at the underlying issue.
@pavelzw that does the trick for me! Thank you!
https://github.com/mamba-org/mamba/actions/runs/5881601796/job/15950428165