Details
Description
Jobs that use newinstall are failing when the miniconda already exists.
Previously, when a miniconda path already existed, even if a user was prompted to install it or it was assumed to install it via the -b option, an installation was not attempted and it was assumed to use that miniconda installation.
Changes from DM-24972 assumed that the miniconda path does not exist if a user asks to install it, either by typing "yes" interactively or using batch mode.
Attachments
Activity
The new changes do the following:
By default, assume we are not installing.
If a user did not specify the path, use the default generated path.
If the generated path does not exist, mark the path for installation by setting do_install = true
If do_install == false, verify the path (auto-generated or user-supplied) has conda installed by checking for the conda command. If the command does not exist, newinstall will fail.
Looks good to me.
To make this more confusing, the tarballs jobs seem like the should be clearing out the directory before running bash newinstall.sh -cb, but that seems like that is not the case.