-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Test cases proving RUSTC_WRAPPER can be a relative path #6638
Test cases proving RUSTC_WRAPPER can be a relative path #6638
Conversation
I'd love to not need to use env::current_dir(), but I couldn't find a way. Also I need to add a test for this. |
Seems plausible to me! This seems a bit deep though within Cargo for where this is handled, could it perhaps be handled at an outer layer where this wrapper is initially set? |
Hmm, maybe! I'll give it a shot. |
58f1067
to
052a176
Compare
Review by @ehuss, perhaps? |
It looks like relative paths are already handled here, so perhaps it could be debugged why that's not working? |
052a176
to
8c26860
Compare
Turns out it was working... |
@bors: r+ Heh well that's a surprise! |
📌 Commit 8c26860 has been approved by |
…crichton Test cases proving RUSTC_WRAPPER can be a relative path Test cases for #4865
☀️ Test successful - checks-travis, status-appveyor |
Update cargo 9 commits in 865cb70106a6b1171a500ff68f93ab52eea56e72..b33ce7fc9092962b0657b4c25354984b5e5c47e4 2019-02-10 15:49:37 +0000 to 2019-02-19 18:42:50 +0000 - Don't retry invalid credentials from git credential helpers (rust-lang/cargo#6681) - Fix some typos in resolver tests (rust-lang/cargo#6682) - Add an unstable option to build proc macros for both the host and the target (rust-lang/cargo#6547) - Test cases proving RUSTC_WRAPPER can be a relative path (rust-lang/cargo#6638) - Add support for Azure DevOps (rust-lang/cargo#6264) - Update docs for removed `patch` restriction. (rust-lang/cargo#6663) - Fix incorrect help message (rust-lang/cargo#6555) - Stabilize Alternative Registries (rust-lang/cargo#6654) - Having a [patch] section when publishing is not an error (rust-lang/cargo#6535)
Test cases for #4865