Skip to content

Commit

Permalink
Use conda env create --yes instead of --force (#45)
Browse files Browse the repository at this point in the history
* Use `conda env create --yes` instead of `--force`.

* Update copyright.
  • Loading branch information
bdice authored Apr 2, 2024
1 parent fc77757 commit d6413a1
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions ci/build_and_test.sh
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
#!/bin/bash
# Copyright (c) 2023, NVIDIA CORPORATION.
# Copyright (c) 2023-2024, NVIDIA CORPORATION.
set -euo pipefail
. /opt/conda/etc/profile.d/conda.sh

Expand All @@ -9,7 +9,7 @@ rapids-dependency-file-generator \
--file_key build \
--matrix "cuda=${RAPIDS_CUDA_VERSION%.*};arch=$(arch);py=${RAPIDS_PY_VERSION}" | tee env.yaml

rapids-mamba-retry env create --force -f env.yaml -n test
rapids-mamba-retry env create --yes -f env.yaml -n test

# Temporarily allow unbound variables for conda activation.
set +u
Expand Down

0 comments on commit d6413a1

Please sign in to comment.