-
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
[compiletest
-related cleanups 2/7] Feed stage number to compiletest directly
#136472
base: master
Are you sure you want to change the base?
Conversation
…--stage-id` Notably, this avoids having to do hacky string splitting based on `--stage-id`.
// FIXME(jieyouxu): improve the communication between bootstrap and compiletest here so | ||
// we don't have to hack out a `stageN`. | ||
let stage = self.config.stage_id.split('-').next().unwrap(); |
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.
Mostly to fix this
This doesn't seem obviously better (we're still hardcoding knowledge in compiletest about the bootstrap folder hierarchy, just adjusting how the base stageN gets threaded). But I'm fine with approving it; my own sense is that tight coupling here is unavoidable given the constraints so I don't care much either way. @bors r+ rollup |
Yeah I really don't think we can avoid assuming knowledge about the folder hierarchy. In fact, tests rely on knowing about this structure for normalization purposes. This PR isn't to get rid of that, it's just make the it slightly less hacky. |
Reference for overall changes: #136437
Part 2 of 7 of the
compiletest
-related cleanups PR series.Summary
--stage
compiletest flag directly from bootstrap, instead of deriving that info in compiletest by doing gymnastics on--stage-id
.r? bootstrap