Something changed in the way conda is activated on CI, so our Windows workaround stopped working. The easiest solution here (after trying to use Bash for Windows in https://github.com/conda/conda-libmamba-solver/pull/525) seems to be using the direct path to Python instead of relying on PATH via activation.
Changes:
Only install the test dependencies for conda-libmamba-solver if we are going to run the conda-libmamba-solver test suite. This is a no brainer, but it fixes a test in test_subcommands where conda-build was injecting its subcommands and they were not expected.
Switch Windows CLS tests to use bash too.
Checklist - did you ...
[ ] Add a file to the news directory (using the template) for the next release's release notes?
Description
Something changed in the way conda is activated on CI, so our Windows workaround stopped working. The easiest solution here (after trying to use Bash for Windows in https://github.com/conda/conda-libmamba-solver/pull/525) seems to be using the direct path to Python instead of relying on PATH via activation.
Changes:
test_subcommandswhereconda-buildwas injecting its subcommands and they were not expected.bashtoo.Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?