-
Notifications
You must be signed in to change notification settings - Fork 707
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
Problems running tests on macOS #1994
Comments
However I have good news! On my Linux box, |
Ahá, so those are the objective-c tests... I guess that's #1954 then. TLDR: Historically we didn't run |
Does this (after updating the tests) help? diff --git a/tests/tests.rs b/tests/tests.rs
index 7bf2c65c..e92d44ce 100644
--- a/tests/tests.rs
+++ b/tests/tests.rs
@@ -305,7 +305,8 @@ fn create_bindgen_builder(header: &PathBuf) -> Result<Builder, Error> {
.unwrap();
flags.extend(extra_flags.into_iter());
} else if line.contains("bindgen-osx-only") {
- let prepend_flags = ["--raw-line", "#![cfg(target_os=\"macos\")]"];
+ // FIXME(#1954): Objective-C tests are broken.
+ let prepend_flags = ["--raw-line", "#![cfg(target_os=\"nonexistent\")]"];
flags = prepend_flags
.iter()
.map(ToString::to_string) Obviously not ideal though... |
It doesn't seem to help. I still get the same
Testing now. |
No matter whether or not I have the #1993 change, I'm going to be away for a few days now so I'm afraid I won't be able to help with further reproduction/diagnosis for a while. But in any case, I'm unblocked because I can run my tests on Linux. Thanks for digging into it! |
OK, I got a chance to dig into this again. The only problem I can still see remaining is #1954, so I'm going to close this. Thanks for help diagnosing! |
Per discussion in #1975 and #1993, tests aren't working for me.
cargo test --all
works in the root directory, but as soon as I docc tests/expectations && cargo test
I get failures. This is what the PR builder bots do, and I want to replicate their results.Here's what I get:
Problems also occur if I use the version from #1993
clang
diagnostics, in case they're relevant:which presumably is the version from homebrew, and perhaps that's the problem.
The text was updated successfully, but these errors were encountered: