-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
bootstrap sets -Zunstable-options
on "check" but not "build", leading to build script reruns
#116538
Comments
Cc @rust-lang/bootstrap |
HEAD: 7cc997d Seems working fine here. |
I'll have to try if I can till reproduce. But note that I mentioned "test build" above, so this would be |
Yeah I can still reproduce the problems with those invocations. (It's not the latest master but recent enough: 3089c31.) Sorry for not giving the exact commands in the issue description. |
I missed the tests part, sorry. I just reproduce it too. I will be working on it by the coming week. @rustbot claim |
We unconditionally set this to avoid recompiling tools between `x check $tool` and `x test $tool` executions. See rust-lang#116538 for more information. Signed-off-by: onur-ozkan <[email protected]>
Rollup merge of rust-lang#117850 - onur-ozkan:fix-116538, r=Mark-Simulacrum bootstrap: simplify setting unstable-options for tools Previously, we unconditionally(instead of `if path == "src/tools/clippy" || ..`) set this (to prevent recompiling tools between `x check $tool` and '` check $another_tool` executions) specifically for tools in the `x check` step. This PR relocates that logic to `fn prepare_tool_cargo`, making it step-agnostic. Fixes rust-lang#116538 Fixes rust-lang#117983
When working on Miri I noticed "portable-atomics" gets rebuilt every time I switch between a check-build and actutally running tests. This boils down to
RUSTFLAGS
being different between the two invocations: in check builds it contains-Zunstable-options
but in test builds it does not.The text was updated successfully, but these errors were encountered: