-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
Allow arguments to JULIA_MPIEXEC #344
Comments
The simplest fix would probably be the following:
However, maybe it is worthwhile to introduce something like |
|
I'd be happy to add something like that, but the question is how spaces should be handled? If we split on spaces, then that prevents the ability to pass variables containing quoted spaces. I'm hoping to move away from the |
Thanks @vchuravy and @simonbyrne for your comments! Maybe quotes could be used when we want to avoid a split on all spaces? Do you see any problem with that? |
@omlins Can you try checking out the |
@simonbyrne , it failed. I made a comment in your branch: 68d8c1d |
Ah, sorry, I have fixed it now, please try again. |
Building worked now:
However testing fails as the JULIA_MPIEXEC_ARGS variable is not yet used there (I guess it should a priori be used in every file where JULIA_MPIEXEC is used):
|
Building MPI with cray-mpich (v7.7.10) works perfectly well, except for the following little issue.
Due to the configuration of our scheduler (SLURM), I need to manually change
deps/build.log
and add-C gpu
or-C mc
to line 89 (note that I setJULIA_MPIEXEC=srun
). I.e. I need to replacewith e.g.
Thus, it would be good to allow arguments to
$mpiexec
for this run command. Even if this fix is very simple, it is important for us as we use automatic build scripts and the requirement of changes in the source code is an obstacle.Thanks!
Here is the error message for completeness:
The text was updated successfully, but these errors were encountered: