-
-
Notifications
You must be signed in to change notification settings - Fork 7
Fix failing Windows wheel builds #55
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
Fix failing Windows wheel builds #55
Conversation
Okay, the unit tests from the test suite are passing fully: https://github.com/pybamm-team/pybammsolvers/actions/runs/17162209565/job/48693989526?pr=55 I cancelled the job because it's going to add another 15 minutes to the workflow run (5-6 minutes per wheel build). I think we should be in a position to merge this now; I'll revert the commits added for testing. |
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.
Great work @agriyakhetarpal! Approving since the previous version ran successfully
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.
Thanks, @agriyakhetarpal 🚀
The SuiteSparse port was split into its substituent packages in the
vcpkg
repodata (see microsoft/vcpkg#41929). Sincevcpkg
versions the ports of its libraries along with itself, the only way to makevcpkg
's builds inmanifest
-mode reproducible is to pin to a specific version of it. From the oldest successful wheel build for PyBaMM before thepybammsolvers
unvendoring, I've switched tovcpkg
v2024.12.16 to fix the Windows wheels. The only difference in these Windows wheel builds after SuiteSparse and SUNDIALS were updated for Linux and macOS in #39 is that we use SUNDIALS v6.5.0 and an older port of SuiteSparse, which brings v5.8.0.This PR should help with the contemporary PRs to build for platforms/architectures. However, I think one of the ways to ease the infrastructure burden going forward would be to migrate to the Meson build system and meson-python build backend, which should be a concerted effort to go in its own PR.
Closes #51