-
-
Notifications
You must be signed in to change notification settings - Fork 122
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
[mpiexecjl] Return exit code of the mpiexec process #834
Conversation
A quick test does some to indicate that this fixes the issue. I am now able to recover exit codes other than |
3dc1925
to
f5ade2b
Compare
@eschnett could you please have a look at the mpitrampoline errors?
I presume we need to update something in the CI setup (unrelated to this PR), but the error message looks a bit contradictory, before it says we have mpiwrapper 2.9, and then it says it's 2.10 |
The error is
We need to use MPIwrapper 2.11 instead. I think I got the semver semantics wrong. The recent change to MPItrampoline (supporting oneAPI) was supposed to be backward compatible, hence the minor version change only. Sorry about this! |
f5ade2b
to
8629957
Compare
Now we get: % mpiexecjl -np 2 --project=/tmp julia --color=yes -e 'exit(2)'; echo $?
┌ Error: The MPI process failed
│ proc = Process(setenv(`/home/mose/.julia/artifacts/b7a943fb6a811908b073b8af69d955f16703ca2b/bin/mpiexec -np 2 julia --color=yes -e 'exit(2)'`,[...]), ProcessExited(2))
└ @ Main none:7
2 which, similarly to what we were doing previously, prints to screen the failed process. |
@giordano I assume your comment above isn't meant for me any more, and that MPItrampoline is now working correctly. |
Yes, I was back to the topic of this PR 🙂 |
Should fix #833. I don't have the time to write tests now though, so opening as draft. @cohensbw could you please test this? With this PR I get