-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Fix broken-pipe-no-ice
run-make test for rpath-less builds
#140843
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
In rare cases, the test may need access to the underlying `std::process::Command` (e.g. for non-trivial process spawning). Co-authored-by: Jesus Checa Hidalgo <jchecahi@redhat.com>
Where host compiler runtime libs are properly configured, instead of raw `RUSTC`/`RUSTDOC` commands. Co-authored-by: Jesus Checa Hidalgo <jchecahi@redhat.com>
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.
Seems like another alternative would be to either implement DerefMut<Command>
for our wrapper, or just implement the stdout/stderr/spawn
functions? But most tests don't need this anyway, so the having the eject logic is also fine by me. Feel free to r=me.
Yeah I considered those options, but it seems really rare to need to implement those.
|
Waiting a bit to hear back from @jchecahi in case this isn't sufficient for them. Locally, the test passes for me when I set |
@jieyouxu yes, this approach fixes the test in my setup too. Thanks for looking into this! |
Fix `broken-pipe-no-ice` run-make test for rpath-less builds The `broken-pipe-no-ice` run-make test currently fails on rpath-less builds, because host compiler runtime libs are not configured for raw std command usages. This PR is an alternative approach to rust-lang#140744. However, instead of duplicating `run_make_support::util::set_host_compiler_dylib_path` logic, we instead support "ejecting" the "configured" underlying std `Command` from `bare_rustc()` and `rustdoc()`, where host compiler runtime libs are already set. cc ``@jchecahi`` r? ``@Kobzol``
…iaskrgr Rollup of 7 pull requests Successful merges: - rust-lang#139863 (rustdoc: Replace unstable flag `--doctest-compilation-args` with a simpler one: `--doctest-build-arg`) - rust-lang#140815 (also export metrics from librustdoc) - rust-lang#140819 (Add regression test for 125877) - rust-lang#140843 (Fix `broken-pipe-no-ice` run-make test for rpath-less builds) - rust-lang#140848 (Improved error message for top-level or-patterns) - rust-lang#140852 (Update the edition guide for let chains) - rust-lang#140864 (Last minute relnotes fix) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#140843 - jieyouxu:broken-pipe, r=Kobzol Fix `broken-pipe-no-ice` run-make test for rpath-less builds The `broken-pipe-no-ice` run-make test currently fails on rpath-less builds, because host compiler runtime libs are not configured for raw std command usages. This PR is an alternative approach to rust-lang#140744. However, instead of duplicating `run_make_support::util::set_host_compiler_dylib_path` logic, we instead support "ejecting" the "configured" underlying std `Command` from `bare_rustc()` and `rustdoc()`, where host compiler runtime libs are already set. cc `@jchecahi` r? `@Kobzol`
The
broken-pipe-no-ice
run-make test currently fails on rpath-less builds, because host compiler runtime libs are not configured for raw std command usages.This PR is an alternative approach to #140744. However, instead of duplicating
run_make_support::util::set_host_compiler_dylib_path
logic, we instead support "ejecting" the "configured" underlying stdCommand
frombare_rustc()
andrustdoc()
, where host compiler runtime libs are already set.cc @jchecahi
r? @Kobzol