-
Notifications
You must be signed in to change notification settings - Fork 557
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
Handle use of RUSTC_WORKSPACE_WRAPPER #1280
Conversation
Works as expected with |
8cae00b
to
479d7f8
Compare
Codecov Report
@@ Coverage Diff @@
## main #1280 +/- ##
==========================================
+ Coverage 29.60% 29.67% +0.07%
==========================================
Files 49 49
Lines 17246 17321 +75
Branches 8304 8333 +29
==========================================
+ Hits 5105 5140 +35
- Misses 6798 6808 +10
- Partials 5343 5373 +30
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Handle the scenario where cargo is being used with sccache as a RUSTC_WRAPPER and another tool is being used as a RUSTC_WORKSPACE_WRAPPER, by looking at whether rustc is the first argument. Signed-off-by: Tom Fay <[email protected]>
the wrapped rustc may not just be "rustc", it may have an extension or more path components
dc42976
to
3d85426
Compare
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.
Looks almost ready to be merged!
Your contribution is very much appreciated!
It'd be great if you could address the few remaining miniscule nits.
Thanks for the review - I've addressed the nits now. |
If CI is passed, we're good to go! Thank you! |
CI is all green 🎉 |
We're just waiting on someone to push the "merge" button, right? |
Fixes #1274
Handle the scenario where cargo is being used with sccache as a RUSTC_WRAPPER and another tool is being used as a
RUSTC_WORKSPACE_WRAPPER, by inspecting the first argument.
In this case
rustc
will be the first argument passed to the workspace wrapper, and therustc
version check will need to also do<wrapper> rustc -vV
rather than<wrapper> -vV
.As a precaution against inadvertently identifying a c compiler as a rustc workspace wrapper, I also checked for the presence of the CARGO env which cargo sets for all processes it runs.