search

mamba-org / setup-micromamba

GitHub Action to set up micromamba
MIT License
97 stars 15 forks source link

micromamba is not recognized as an internal or external command 2.0.0 #227

Open ktsitsi opened 5 days ago

ktsitsi commented 5 days ago

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.

Run micromamba run -n test pre-commit run -a

Taking a look at the logs the only difference we notice is that micromamba info was now fetching 

libmamba version : 2.0.0
micromamba version : 2.0.0

We were able to resolve by pinning to mamba-org/setup-micromamba@v1.9.0 with the micromamba-version: 1.5.10-0 following similar approach as commented in https://github.com/mamba-org/setup-micromamba/issues/225

Runner Logs here

jeremyleung521 commented 22 hours ago

Was hoping mamba=2.0.1 would fix this (there was a fix for a windows bug on mamba activate), but that doesn't seem to be case. Not sure if this is a problem on setup-micromamba's end or regular mamba's end?

Runner Logs: https://github.com/jeremyleung521/LPATH/actions/runs/11088430490/job/30931937962#step:4:362 Note: Can't see that it's running 2.0.1 in the windows jobs due to the order things are printed, but the other tests (macos, ubuntu) do say that 2.0.1 is pulled.

EDIT: It's being tracked here: https://github.com/mamba-org/mamba/issues/3478

pavelzw commented 7 hours ago

i would expect that this is a micromamba issue. wdyt @jjerphan?

jjerphan commented 6 hours ago

It is. There's a problem with the activation script on Windows as of micromamba 2.0. We are currently addressing the problem.