Closed traversaro closed 2 years ago
we may require the same gcc version in the ci?
if manifpy has an hard constraint on the gcc version used that should be reflected somehow in the CI.
Perhaps we need to install pybind11-abi
as well? Totally random guess (see https://conda-forge.org/docs/maintainer/knowledge_base.html#pybind11-abi-constraints).
Indeed, the problem was solved by https://github.com/conda-forge/manif-feedstock/pull/18, see https://github.com/ami-iit/bipedal-locomotion-framework/runs/5365668442 . I think we can close the issue as the problem is tracked on the manif conda-forge side at https://github.com/conda-forge/manif-feedstock/issues/19 .
Related issue: https://github.com/ami-iit/bipedal-locomotion-framework/issues/386 .
@GiulioRomualdi noticed a CI failure in test using manifpy pybind11 objects, something like:
I looked at the history, and found that the difference in conda environments between the latest working job (~8 days ago) and the first failing (~7 days ago) is:
The problem seems indeed the update from gcc 9 to gcc 10, and the fact that
manifpy 0.0.4 py39he14f5cb_6
was built with gcc 9. https://github.com/conda-forge/manif-feedstock/pull/18 should solve the immediate problem, but probably we need to understand how to handle this properly: if manifpy has an hard constraint on the gcc version used that should be reflected somehow in the CI.