You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched open reports and couldn't find a duplicate
What happened?
I have CI set up to build a constructor based installer. I had a recent successful build moorepants/anaconda-dee-config#17 with constructor 3.11.1 and then I removed version pins of all packages in construct.yaml to test solving an up-to-date set of packages in moorepants/anaconda-dee-config#18 but the second build failed to install. The failure gave this error:
Setup environment variables...
Add "C:\Users\runneradmin\miniconda3\condabin" to PATH
Set 'CONDA="C:\Users\runneradmin\miniconda3"'
Parsing environment...
Applying initial configuration...
Warning: The 'defaults' channel might have been added implicitly. If this is intentional, add 'defaults' to the 'channels' list. Otherwise, consider setting 'conda-remove-defaults' to 'true'.
Adding pkgs_dir 'C:\Users\runneradmin\conda_pkgs_dir'
Error: No existing conda executable found at any of C:\Users\runneradmin\miniconda3\condabin\conda.bat,C:\Users\runneradmin\miniconda3\Library\bin\conda.exe
This came from building with the latest released version of constructor 3.11.1.
I then switched to constructor < 3.10 and the build succeeded:
Checklist
What happened?
I have CI set up to build a constructor based installer. I had a recent successful build moorepants/anaconda-dee-config#17 with constructor 3.11.1 and then I removed version pins of all packages in
construct.yaml
to test solving an up-to-date set of packages in moorepants/anaconda-dee-config#18 but the second build failed to install. The failure gave this error:This came from building with the latest released version of constructor 3.11.1.
I then switched to
constructor < 3.10
and the build succeeded:moorepants/anaconda-dee-config#18
I am not sure what may be different, but maybe this points to an issue introduced after version 3.9.3.
Additional Context
No response
The text was updated successfully, but these errors were encountered: