On 4/13/2012 6:40 PM, Ralph Castain wrote:
Did you have the param set? I found some missing code in the orted
errmgr that contributed to it, but unless you had set the param in
your test, there is no way it would abort no matter how many procs
exit with non-zero status.
Is mpirun sticking aro
Did you have the param set? I found some missing code in the orted errmgr that
contributed to it, but unless you had set the param in your test, there is no
way it would abort no matter how many procs exit with non-zero status.
I'm guessing you have that param set in your test due to our earlier
I could see if less then N processes exit with non-zero exit code that
the ORTE may choose not to abort the job. However, if all N processes
have exited or aborted I expect everything to clean up and mpirun to
exit. It does not do that at the moment which I think is what is
causing most of th
