-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
stabilize stage management for rustc tools #137215
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
f012427
handle `ToolRustc` build stages automatically
onur-ozkan 164f240
pass target_compiler from Rustdoc
onur-ozkan 7638abb
bless tests
onur-ozkan 72e67e8
return more advanced type from `ToolBuild`
onur-ozkan 8e011e5
migrate llvm-bitcode-linker to `ToolBuild`
onur-ozkan a338439
return `ToolBuildResult` to utilize them from callers
onur-ozkan 6cf650f
remove manually handled stage offs
onur-ozkan 5e5b1b0
document tool implementations
onur-ozkan baef666
adapt tool module to `ToolBuildResult`
onur-ozkan 60ade6c
add test coverage for `tool::get_tool_rustc_compiler`
onur-ozkan 26f588b
fix cargo tests
onur-ozkan 5408aae
fix rust-analyzer tests
onur-ozkan 26d6ce7
add rustc-dev doc about bootstrap tools
onur-ozkan b4a3b64
set `build.test-stage = 2` for `tools` profile
onur-ozkan 4b9b5d7
add change-entry for tools profile update
onur-ozkan 76063a6
print warning and help messages
onur-ozkan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I don't think this is a good default -- it should be considered a bug if the tests do not work in stage 1. Certainly, they do work for Miri, so this can lead to Miri contributors waiting unnecessarily long for their builds to finish.
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.
#137522 should be enough for the stage1 problems happen on clippy and cargo tests, so this should be revertable.
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.
So what that does is just bump the stage to 2? I guess that hides the bugs with those tools...
I have #78717 somewhere in my TODO list, so I'll have to remember to revert that then. I don't know why cargo needs stage 2.
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.
I didn't get how #78717 is being related to
test-stage = 2
in the config file.Actually I don't know if it's a bug or not. All other tools work fine but cargo and clippy fail on stage 1 tests.
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.
#78717 tracks the bug that you need stage 2 for clippy. Once that is fixed, clippy can be tested on stage 1.
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.
I am arguing that we should consider it a bug. We should have the expectation that tools can be tested in stage 1 (except when they really need the bootstrap loop to have completed, which is quite rare).