-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
micromamba is not recognized as an internal or external command 2.0.0 #227
Comments
Was hoping Runner Logs: https://github.com/jeremyleung521/LPATH/actions/runs/11088430490/job/30931937962#step:4:362 EDIT: It's being tracked here: mamba-org/mamba#3478 |
i would expect that this is a micromamba issue. wdyt @jjerphan? |
It is. There's a problem with the activation script on Windows as of micromamba 2.0. We are currently addressing the problem. |
2.0.2 is being released and should fix this issue. |
Thank you! Just have to wait for |
I just updated to v2 (2.0.2) and still having the same problem... :/ Though this time, it's failing in the 'pip' section of the environment file.
Log file: https://github.com/jeremyleung521/LPATH/actions/runs/11182636779/job/31089361519#step:4:370 EDIT: It's this bug: mamba-org/mamba#3467. |
Yesterday we noticed a failure in our CI only on the
windows-latest
runner where we were getting the following error:'"C:\Users\runneradmin\micromamba\condabin\micromamba"' is not recognized as an internal or external command, operable program or batch file.
using the
mamba-org/setup-micromamba@v1
. while running a simple pre-commit check using the env.Taking a look at the logs the only difference we notice is that
micromamba info
was now fetching
We were able to resolve by pinning to
mamba-org/[email protected]
with themicromamba-version: 1.5.10-0
following similar approach as commented in #225Runner Logs here
The text was updated successfully, but these errors were encountered: