Skip to content

CI: recreate conda env from conda-forge to avoid mixed-channel solve #19255

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.

Sign up for GitHub

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

Closed
rascani wants to merge 1 commit into from
+16 −1
Closed

CI: recreate conda env from conda-forge to avoid mixed-channel solve #19255

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion .ci/scripts/setup-conda.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,22 @@ set -ex

install_conda() {
pushd .ci/docker || return
${CONDA_INSTALL} -c conda-forge -y --file conda-env-ci.txt

# The env created by pytorch/test-infra's setup-miniconda is pre-populated
# with cmake=3.22 ninja=1.10 pkg-config=0.29 wheel=0.37 from the anaconda
# defaults channel. Mixing those with conda-forge's newer transitive deps
# required by our cmake=3.31.2 pin (libzlib>=1.3.1, rhash>=1.4.5) has been
# intermittently failing the libmamba solver, especially on ephemeral
# GitHub-hosted macOS runners where the env is fresh every job. Tear down
# the pre-populated env and recreate it from conda-forge only so the solve
# never has to reconcile two channels.
PY_VERSION=$(conda run -p "${CONDA_PREFIX}" python -c \
'import sys; print(f"{sys.version_info.major}.{sys.version_info.minor}")')

conda env remove --prefix "${CONDA_PREFIX}" -y
conda create --prefix "${CONDA_PREFIX}" -c conda-forge --override-channels -y \
"python=${PY_VERSION}" --file conda-env-ci.txt

popd || return
}

Expand Down
Loading