-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Remove ONLY_BUILD and ONLY_BUILD_TARGETS #48599
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
Remove ONLY_BUILD and ONLY_BUILD_TARGETS #48599
Conversation
This seems plausible to me! I think you know more about these variables now than I do, but for me the correctness of the PR is mostly determined by what happens on Travis. Could you run some of the containers locally like a cross dist and cross tests to make sure everything is working? Historically these changes tend to cause an extra step or two to get run on CI which goes undiagnosed for awhile :( |
541e308
to
85bd2f6
Compare
I've edited the first two commits and rechecked, and I feel that both the I probably won't have time to run dist/cross jobs locally and compare them until at least this weekend, and to an extent have less confidence in my ability to do so correctly than what I've already done here -- but will get back to you with results afterwards. |
All cases where it is used can be replaced by substituing run.host for run.builder.build.build; that is its only effect. As such, it is removable.
All uses are replaced with not accessing run.target/run.host, and instead directly using run.builder.build.build.
Previously it was set to true when we didn't run HOSTS steps.
761fb27
to
29a8529
Compare
I've manually verified and I feel pretty good about this -- I couldn't find any differences, and the current PR state is intended to be logically sound (even more so than before). r? @alexcrichton |
impl Step for Src { | ||
type Output = (); | ||
const DEFAULT: bool = true; | ||
const ONLY_HOSTS: bool = true; |
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.
Hm doesn't this mean that we'll be producing the dist-src package on all dist builders now?
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.
This is the install step; we don't run install on CI. The dist::Src
step hasn't changed the conditions it runs on. Neither has this step; I just pulled it out because the macro creates the struct with too many fields for Src... I can go into more detail if necessary, it's somewhat complicated.
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.
Er right sorry I mixed this up with dist::Src
, my bad!
@bors: r+ |
📌 Commit 29a8529 has been approved by |
@bors rollup |
…tep-1, r=alexcrichton Remove ONLY_BUILD and ONLY_BUILD_TARGETS Primarily removes `ONLY_BUILD` and `ONLY_BUILD_TARGETS`. These aren't actually needed in the new system since we can simply not take the relevant `host` and `target` fields if we don't want to run with them in `Step::make_run`. This PR also includes a few other commits which generally clean up the state of rustbuild, but are not related to the `Step` changes.
…tep-1, r=alexcrichton Remove ONLY_BUILD and ONLY_BUILD_TARGETS Primarily removes `ONLY_BUILD` and `ONLY_BUILD_TARGETS`. These aren't actually needed in the new system since we can simply not take the relevant `host` and `target` fields if we don't want to run with them in `Step::make_run`. This PR also includes a few other commits which generally clean up the state of rustbuild, but are not related to the `Step` changes.
…tep-1, r=alexcrichton Remove ONLY_BUILD and ONLY_BUILD_TARGETS Primarily removes `ONLY_BUILD` and `ONLY_BUILD_TARGETS`. These aren't actually needed in the new system since we can simply not take the relevant `host` and `target` fields if we don't want to run with them in `Step::make_run`. This PR also includes a few other commits which generally clean up the state of rustbuild, but are not related to the `Step` changes.
…excrichton Remove ONLY_BUILD and ONLY_BUILD_TARGETS Primarily removes `ONLY_BUILD` and `ONLY_BUILD_TARGETS`. These aren't actually needed in the new system since we can simply not take the relevant `host` and `target` fields if we don't want to run with them in `Step::make_run`. This PR also includes a few other commits which generally clean up the state of rustbuild, but are not related to the `Step` changes.
☀️ Test successful - status-appveyor, status-travis |
Primarily removes
ONLY_BUILD
andONLY_BUILD_TARGETS
. These aren't actually needed in the new system since we can simply not take the relevanthost
andtarget
fields if we don't want to run with them inStep::make_run
.This PR also includes a few other commits which generally clean up the state of rustbuild, but are not related to the
Step
changes.