Bootstrap rustc wrapper verbosity not tracked
Open
Nobody has claimed this yet.
C-bug
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
x build -vvv
this causes lots of output from the rustc wrapper.
x build
cargo then caches the output from the rustc wrapper, not realizing the the var used to control this has been changed.
I'm not sure what the easiest way would be to make cargo aware of it, it would somehow have to end up in the dep file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior with x build -vvv followed by x build, focusing on Cargo's handling of the rustc wrapper output cache. Investigate how the verbosity variable is represented in the dependency file and determine what would make Cargo notice when it changes. Done means the second build does not reuse output produced with different wrapper verbosity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100