-
Notifications
You must be signed in to change notification settings - Fork 53
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
configury: update much configury to OMPI main #1130
Conversation
20db94e
to
c0dd8d0
Compare
aligns with ompi main branch ref: cebad71e4f50d49e486ccd54668cf58698556a7c
c0dd8d0
to
30c81e2
Compare
I took a cursory look at the code generated and it looks fine to me. Generated code is notoriously difficult to audit for correctness. I will +1 it, but I think we should add some tests (perhaps in CI) to validate that the parameters provided by configure work as advertised. |
I agree, I feel we should strive to have test cases either through direct (code) testing or via CI coverage in general. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did a local build, all logs look cleaner and no errors. Thanks Dave.
You might be surprised to learn that this code is not generated for the most part - I'm pretty sure many humans have contributed to OMPI's configury over the years. For example, this is the commit history on the UCX config file:
The existing CI has pretty good coverage on the changes in this PR. Here are some pointers to where that happens in the SOS ci.yml file:
That said, it's not perfect coverage. We're not testing scenarios where the path is not provided explicitly, for example.
I double checked Anyway, does that address the concerns or am I missing something? One issue with this PR is that I integrated with a particularly random upstream commit... I believe at the time I did this work, the latest OMPI release had some configury issue, but I can't recall exactly... Maybe it's better to try to align with a newer release, but I don't see a strong need as long as we take note of where exactly we're cribbing this from. The license coverage should be good unless we missed something in the past. Only the |
@davidozog thanks for the change set and the insights. Please merge in when ready. |
This PR aligns SOS's configury with OMPI's main branch ref cebad71e
It removes several configure-time warnings about obsolete autotools features and adds relevant updates for OFI (esp. for HMEM), UCX, and Portals4.
All changes from
OMPI/config/*
are verbatim, andSOS/configure.ac
was run throughautoupdate
.