-
-
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
MPIPreferences + Test #715
Comments
Okay, so the advice should generally be that if your package uses MPI in its tests, it should have MPIPreferences in its test dependencies? |
@simonbyrne Until it's fixed upstream, yes, that's the recommendation. |
@carstenbauer : so putting the following in the project.toml of a package would work? [targets]
test = ["Test", "MPIPreferences"] |
Yes, you also need: [extras]
MPIPreferences = "3da0fdf6-3ccc-4f1b-acd9-58baa6c99267" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Probably a more general/upstream issue but I'll post it here nonetheless, because this is where I encountered it. (UPDATE: JuliaLang/Pkg.jl#3389)
In short, the issue is that
] test
doesn't seem to respect theJULIA_LOAD_PATH
variable and thus global preference files.On our cluster, we provide a global
Project.toml
(say at/some/global/path/Project.toml
) in which we set the MPI preferences, specificallyWe then automatically set
JULIA_LOAD_PATH=:/some/gobal/path
when the user loads the julia module. This works just fine in a regular Julia session where one getsHowever, when running
] test
theJULIA_LOAD_PATH
env variable is ignored and one only getsThis means that the global MPI preferences are not respected, leading to undesired behavior and, in my specific case, an indefinite hang.
The text was updated successfully, but these errors were encountered: