-
Notifications
You must be signed in to change notification settings - Fork 48
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
2022.02 release CI dry run #1046
Comments
These are the problems: P1Conda packages generation on macOS, as described in #1041 . P2Conda metapackaages generation on Windows and Linux:
P3Windows-vcpkg build failure:
|
P3 is quite easy to solve, even if it requires a change in HDE. Interestingly it seems we already solved it (see #352 (comment)), let's see what went wrong. |
I suspect P2 is related to #1047, as an older cppad was forced, and so an older bipedal-locomotion-framework is used. I try to trigger a new dry run after updating the version to see if this fixes the problem: |
Indeed that solved P2, at least for Windows and Linux. I just tried to install (note that I used 2022.03.0 as this is the experimental version that I created):
And it is working fine. The problem is that |
New dry run in https://github.com/traversaro/robotology-superbuild/runs/5346558463 failed due to metapackages and the combination of #1049 and pinning qt in the metapackages. Better to find a better solution soon, testing now via https://github.com/traversaro/github-actions-tmate/actions . |
By manually installing a possible compromise of pin is gazebo=11.9 (not 1.10 that is broken, see ), libopencv=4.5.3 (that is homewever different from the current version pinned in conda-forge, that is 4.5.5) and qt |
Even with those pins, the
or
For some reason, the mamba solver is picking old version from the robotology channel instead of the one from |
In the end, we went for the modifications in #1049, disabling for now the generation of metapackages on macOS . |
I did a 2022.02 release dry run in:
To check if the CI (that is quite more complex since #1030) is working fine.
The release dry run will not interfere with the regular releases as it is done in a fork.
The text was updated successfully, but these errors were encountered: