You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution to issue cannot be found in the documentation.
I checked the documentation.
Issue
In testing an installation on Github Actions (example job), I have encountered an issue where after installing mpi via conda on a job running the MacOS 12.0 image, the mpi executables (mpiexec, mpicc, etc.) cannot be located. conda reports that mpi is installed (along with mpich by default), but inspection of the conda bin directory confirms that they are not present. This problem does not occur on the MacOS 11.0 image and occurs with both mpich and openmpi when specified explicitly. I am not sure if this is an issue with the runner image or the conda installation and will redirect if this is not the right place to report, but I am starting here as I believe this metapackage is used by both mpich and openmpi. Thanks! - Meagan
@langmm This is the wrong repo to report to. The mpi package here is just a mutex, to ensure you only have either openmpi or mpich installed, as they cannot coexist.
The issue in your env is this
mpich 4.0.3 external_0 conda-forge
for some reason you installed the "empty" mpich package (note the build string says "external"). It does not come with the actual library or executable. It's there only to satisfy the conda solver requirement, so that users can use their local MPICH installation. You should reinstall your mpich.
Solution to issue cannot be found in the documentation.
Issue
In testing an installation on Github Actions (example job), I have encountered an issue where after installing mpi via conda on a job running the MacOS 12.0 image, the mpi executables (mpiexec, mpicc, etc.) cannot be located. conda reports that mpi is installed (along with mpich by default), but inspection of the conda bin directory confirms that they are not present. This problem does not occur on the MacOS 11.0 image and occurs with both mpich and openmpi when specified explicitly. I am not sure if this is an issue with the runner image or the conda installation and will redirect if this is not the right place to report, but I am starting here as I believe this metapackage is used by both mpich and openmpi. Thanks! - Meagan
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: