-
Notifications
You must be signed in to change notification settings - Fork 52
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
Regression in supported interconnects #63
Comments
To get it get it to use rdma inside the prefix layer I needed to explicitly provide the path:
Just setting |
This is not really an issue with the prefix layer, I'm going to move it |
I also checked
which I would also have suspicions about. |
I checked our |
I see that the
As the compiler has been configured with |
This has been fixed in
We should still have some (ReFrame?) test for this to make sure that UCX is always correctly configured in future versions, though, so let's leave this issue open to not forget about this. |
Sync branch for rebuilding `generic` with branch for NESSI/2022.11
I was looking at the UCX configuration in
2020.12
and I noticed that it looks like we have a regression. From EESSI/compatibility-layer#49 (comment) it looks like we should have a UCX configuration likebut in the build log for UCX (on Zen2) I see
(note the missing
rdmacm
)We should probably explicitly insert what we expect from the final build (
--with-rdmacm
) so that configure will fail rather than build regardless. UCX in particular is critical to the stack so could do with additonal checks.The text was updated successfully, but these errors were encountered: