Closed leofang closed 3 years ago
Is this still the case if one changes...
...to...
ignore_run_exports:
- cudatoolkit
?
Wondering if ignore_run_exports_from
might not be working as expected, but perhaps ignore_run_exports
would
Could it be a bug in conda
? I just tested on another machine that also has a GPU and an older conda, and it doesn't show up:
$ conda install -c conda-forge mpi4py openmpi
Collecting package metadata (current_repodata.json): done
Solving environment: done
==> WARNING: A newer version of conda exists. <==
current version: 4.7.12
latest version: 4.9.2
Please update conda by running
$ conda update -n base -c defaults conda
## Package Plan ##
environment location: /home/leofang/miniconda3/envs/cupy_dev_cuda11
added / updated specs:
- mpi4py
- openmpi
The following packages will be downloaded:
package | build
---------------------------|-----------------
ca-certificates-2020.12.5 | ha878542_0 137 KB conda-forge
certifi-2020.12.5 | py37h89c1867_1 143 KB conda-forge
mpi4py-3.0.3 | py37h3e1c8c0_4 703 KB conda-forge
openssl-1.1.1i | h7f98852_0 2.1 MB conda-forge
------------------------------------------------------------
Total: 3.1 MB
The following NEW packages will be INSTALLED:
mpi conda-forge/linux-64::mpi-1.0-openmpi
mpi4py conda-forge/linux-64::mpi4py-3.0.3-py37h3e1c8c0_4
openmpi pkgs/main/linux-64::openmpi-4.0.2-hb1b8bf9_1
The following packages will be UPDATED:
ca-certificates 2020.6.20-hecda079_0 --> 2020.12.5-ha878542_0
certifi 2020.6.20-py37hc8dfbb8_0 --> 2020.12.5-py37h89c1867_1
openssl 1.1.1g-h516909a_1 --> 1.1.1i-h7f98852_0
But oddly, all CI tests do not have this problem either...
Certainly possible, in which case my suggestion above may not help
Are you able to isolate the Conda version that has the bug?
The CI is running on the latest conda, right?
I couldn't reproduce this consistently, closing this for now.
Looks like the build time dependency on
cudatoolkit
leaks out to runtime...😞