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

tests: Guess modern libclang version when we fail to parse a version. #1993

Merged
merged 1 commit into from
Feb 15, 2021

Conversation

emilio
Copy link
Contributor

@emilio emilio commented Feb 13, 2021

Should fix the test failures described in #1991 and #1975 on modern Mac.

Should fix the test failures described in #1991 and #1975 on modern Mac.
@emilio
Copy link
Contributor Author

emilio commented Feb 13, 2021

@adetaylor @hlopko, can you confirm that with this patch, cargo test passes on your machine?

@hlopko
Copy link
Contributor

hlopko commented Feb 15, 2021

I've uploaded #1996 that fixes the problem for me on my linux and mac machines.

I personally would prefer if bindgen panicked when it cannot parse the clang version, but I can imagine some workflows would benefit from setting the default as implemented in this PR.

@emilio
Copy link
Contributor Author

emilio commented Feb 15, 2021

Yeah, this is only used for testing and for an old-clang-workaround (where we already treat "unknown" as "modern"), so this is consistent with that.

@emilio emilio merged commit e59aa92 into master Feb 15, 2021
@emilio emilio deleted the test-version-modern branch February 15, 2021 13:06
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.

3 participants