If you ask mpirun to launch an executable that does not exist, it fails, but returns an exit status of 0. This makes it difficult to write scripts that invoke mpirun and need to check for errors. I'm wondering if a) this is considered a bug and b) whether it might be fixed in a near term release.

Example:

> orterun -np 2 asdflkj
------------------------------------------------------------------------ --
Failed to find the following executable:

Host:       build-linux64
Executable: asdflkj

Cannot continue.
------------------------------------------------------------------------ --
> echo $?
0


I see this behavior for both 1.2 and 1.1.x.

Thanks for your help.

Bill

Reply via email to