mtt icon indicating copy to clipboard operation
mtt copied to clipboard

Enhance Python client to facilitate debugging errors in MPI build phase

Open hppritcha opened this issue 5 years ago • 0 comments

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 Get name>/<MPI Install name>/<MPI version number>/mpi_installed_vars.sh /installs/<MPI Get name>/<MPI Install name>/<MPI version number>/mpi_installed_vars.csh Hence, you can source these files like this (assuming a csh-flavored shell):

shell% cd /installs/<MPI Get name>/<MPI Install name>/<MPI version number> 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.

hppritcha avatar Dec 18 '19 17:12 hppritcha