[workspace] Upgrade osqp and qdldl to latest versions #22855
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 ofqdldl
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 withqdldl
in a more robust manner, appearing to point to a stable release rather than a specific commit hash. Furthermore, the stable release ofqdldl
thatosqp v1.0.0
points to is0.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 intools/workspace/qdldl_internal/README.md
no longer exists as a result of repository refactoring changes in the latest version ofosqp
, 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