Conversation
…nda-forge-pinning 2024.04.02.08.31.27
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Windows tests on Python are failing with: The error is vaguely familiar. |
|
See #25 (comment) . |
|
Successful builds are using pybind11 2.11.0, while the failing Windows builds is using pybind11 2.12.0
The error is also upstream: gbionics/bipedal-locomotion-framework#829 . I think is related to pybind11 2.12.0 . |
|
Found some related PRs:
In a nutshell, it seems that since pybind11==2.12.0 there is an incompatibility between pybind11 extension using different versions of MSVC compiler. I think we can just pin pybind11 to be <2.12.0 for now. |
As a workaround fro conda-forge/pybind11-feedstock#94 (comment) .
This PR has been triggered in an effort to update idyntree12.
Notes and instructions for merging this PR:
Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.
If this PR was opened in error or needs to be updated please add the
bot-rerunlabel to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase@conda-forge-admin, please rerun botin a PR comment to have theconda-forge-adminadd it for you.This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8531760838, please use this URL for debugging.