Skip to content
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.

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

Enhance Python client to facilitate debugging errors in MPI build phase #890

Open
hppritcha opened this issue Dec 18, 2019 · 0 comments
Open

Comments

@hppritcha
Copy link
Member

From an issue @DebRez originally opened for different issue but should probably have its own issue. Below describes a mechanism available with the perl MTT client to debug MPI build issues. Something like it would be a nice enhancement for the Python client:

==========================

MPI Install Errors
Sometimes MTT finds a problem in a middleware install, but a human wants to go examine it manually. When MTT installs a middleware under its scratch tree, it will automatically drop two files – one for sh-flavored shells and one for csh-flavored shells – that set the PATH and LD_LIBRARY_PATH to get to the middleware install. The exact location of these files depends on the section names in your INI file and the exact version number of the MPI in question. Specifically, these files will be in:

/installs////mpi_installed_vars.sh
/installs////mpi_installed_vars.csh
Hence, you can source these files like this (assuming a csh-flavored shell):

shell% cd /installs///
shell% source mpi_installed_vars.csh
Mpicc, mpirun, etc. will then be in your PATH, and the appropriate libraries will be in your LD_LIBRARY_PATH. Additionally, the environment variable MPI_ROOT will be set that points to the top-level installation directory for the middlewareBuild. This is useful with Open MPI’s --prefix option to mpirun, for example. Note that all the files related to the testing of that MPI are under this tree – the source tree, the tests, etc. So you can go examine the entire test – not just put the MPI in question in your path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant