Skip to content

[workspace] Upgrade osqp and qdldl to latest versions #22855

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

Closed

Conversation

Aiden2244
Copy link
Contributor

@Aiden2244 Aiden2244 commented Apr 2, 2025

Towards #22836

These upgrades produced build failures in local testing. Furthermore, there have been changes regarding how the osqp upstream keeps track of its targeted version of qdldl that render our current documentation regarding this upgrade obsolete. Namely, osqp had a major version release since this time last month, and it would now appear that it handles its integration with qdldl in a more robust manner, appearing to point to a stable release rather than a specific commit hash. Furthermore, the stable release of qdldl that osqp v1.0.0 points to is 0.18, which happens to be the same version that Drake wanted to upgrade to. There is a chance we may no longer need to keep track of these dependencies separately anymore and may be able to rely on the auto-update tool. What is known for certain is that the path referenced in tools/workspace/qdldl_internal/README.md no longer exists as a result of repository refactoring changes in the latest version of osqp, so at a minimum that reference will have to be removed once these upgrades land.

Problematic everything release job: linux-jammy-clang-bazel-experimental-everything-release


This change is Reviewable

@jwnimmer-tri
Copy link
Collaborator

I will dig into this at some point.

@jwnimmer-tri jwnimmer-tri self-assigned this Apr 3, 2025
@jwnimmer-tri jwnimmer-tri added the release notes: fix This pull request contains fixes (no new features) label Apr 3, 2025
@jwnimmer-tri
Copy link
Collaborator

Replaced by #22870.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release notes: fix This pull request contains fixes (no new features) status: do not review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants