-
Notifications
You must be signed in to change notification settings - Fork 250
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
Add pybind11_abseil #2031
Add pybind11_abseil #2031
Conversation
Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (pybind11_abseil) have been updated in this PR. Please review the changes. |
467b48b
to
6d66461
Compare
As discussed internally, I propse @frigus02 as maintainer. Are you willing to accept? |
@fmeum could you please trigger the tests? |
I accept |
bcf6d74
to
072b9ec
Compare
@fmeum could you please trigger the tests? |
Anyone has an idea why the tests can't find |
It's because of |
@fmeum Would there be any problems with just removing this? |
c0a6b86
to
dfac6dd
Compare
@fmeum Hmm. Even after removing the |
It's still failing, but for a different reason. You may just need to pass in |
bed4fda
to
faae23c
Compare
@fmeum Thanks. Linux builds seem to run fine with Windows tests now fail with
What is the best way to set a minimum C++ version across all supported OSes? |
If it helps, RE2 does this. |
@junyer IIUC |
faae23c
to
b49fafa
Compare
MacOS fails with
Any idea what could be wrong here? |
Windows now fails with
|
https://buildkite.com/bazel/bcr-presubmit/builds/5056#018f2f66-e390-4cb3-9159-7c13bd0741d0 indicates otherwise:
|
b49fafa
to
e47f928
Compare
I removed tests for Windows and MacOS as upstream also doesn't test this: https://github.com/pybind/pybind11_abseil/blob/master/.github/workflows/actions.yml. Tests are passing now. |
This is using the same patches as in #2031. As there is no release process, we are using a version string including the commit sha like it's done for `boringssl` as well.
This is using the same patches as in bazelbuild#2031. As there is no release process, we are using a version string including the commit sha like it's done for `boringssl` as well.
No description provided.