-
Notifications
You must be signed in to change notification settings - Fork 352
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
auto-detect no_std where possible #3000
Conversation
cargo-miri/src/setup.rs
Outdated
|| target.contains("nvptx") | ||
|| target.contains("switch") | ||
|| target.contains("-uefi"); | ||
let sysroot_config = if no_std || std::env::var_os("MIRI_NO_STD").is_some() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to be able to disable the heuristic with MIRI_NO_STD=0
?
Ah, the test suite also checks the env var, for building the dependencies Line 97 in defbb66
I don't think I want to repeat the target name check there, that seems a bit too ugly... |
I wonder if we could have ui_test only build the dependencies if at least one test matches the filter? That would elegantly avoid the need for the |
Yea, I'm working on this, but it's a bigger refactoring to do it nicely. If you want it fast I can build a hacky version of it. |
Nah, this is not urgent. |
Marking as blocked on #3008 |
this is happening now |
7822ab9
to
10617d6
Compare
Looks like that is working. :) |
@bors r+ |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
r? @oli-obk
Cc https://rust-lang.zulipchat.com/#narrow/stream/269128-miri/topic/restricted_std.20sysroot.3F