-
Notifications
You must be signed in to change notification settings - Fork 1.7k
For toolchain binaries use the full path found in $PATH #16755
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
Conversation
@MabezDev this reverts your recent PR, but if I understood the issue you had correctly, my changes in here should not break your workflow again (we now invoke the full path found in $PATH instead of just the binary name if we find a working path in $PATH). |
Unfortunately, this does break my workflow. I checked out this PR and installed locally, replacing my binary which contained my original PR.
It's still trying to use my system Rust, and not the rustup installation. |
That's odd, you said " My |
Oh wait, you literally have |
So I added the source to |
i'll try this with a buck2-built sysroot once some issues at work are resolved. |
Does this work? |
✌️ @davidbarsky, you can now approve this pull request! If @Veykril told you to " |
it does! |
☀️ Test successful - checks-actions |
1 similar comment
☀️ Test successful - checks-actions |
👀 Test was successful, but fast-forwarding failed: 422 Changes must be made through a pull request. |
Fixes #16754