Skip to content
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

Constraint pybind11 version to fix conda-forge Windows CI #831

Merged
merged 6 commits into from
Apr 4, 2024

Conversation

traversaro
Copy link
Collaborator

@traversaro traversaro commented Apr 3, 2024

Fix #829, add workaround for conda-forge/pybind11-feedstock#95 .

@traversaro
Copy link
Collaborator Author

I have no idea why, but pybind11<2.12.0 continue to fail on Windows with:

bash: line 1: 2.12.0: No such file or directory

@GiulioRomualdi
Copy link
Member

Now the windows CI compiles but the test fails as before, i.e., it's not able to find manifpy

@traversaro
Copy link
Collaborator Author

traversaro commented Apr 4, 2024

Now the windows CI compiles but the test fails as before, i.e., it's not able to find manifpy

The wrong version of pybind11 is still installed.

@traversaro
Copy link
Collaborator Author

There are a lot of unrelated network failures in conda CI, probably related to conda/infrastructure#899 and conda/infrastructure#906 .

@traversaro
Copy link
Collaborator Author

Ok, beside the network failures I found a configuration that on Windows is installing the correct version of pybind11.

@GiulioRomualdi
Copy link
Member

It works! Merging!

@GiulioRomualdi GiulioRomualdi merged commit f0fba60 into master Apr 4, 2024
11 of 15 checks passed
@GiulioRomualdi GiulioRomualdi deleted the fixwin branch April 4, 2024 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows Conda CI Failure April 2024
2 participants