about summary refs log tree commit diff
path: root/src/test/incremental/thinlto
diff options
context:
space:
mode:
authorEduard-Mihai Burtescu <edy.burt@gmail.com>2017-02-25 14:13:17 +0200
committerGitHub <noreply@github.com>2017-02-25 14:13:17 +0200
commite31d46402d1804ba4989665ffb8d9ce2c7686ad0 (patch)
tree517a15c76c0655d4dc074b57883ef54f2d32cc9a /src/test/incremental/thinlto
parentad9079bae4250b2f9e99162d3ea14a1a90201a81 (diff)
parent0e45a5ed3f79338656b19a41172d3a7761586ebc (diff)
downloadrust-e31d46402d1804ba4989665ffb8d9ce2c7686ad0.tar.gz
rust-e31d46402d1804ba4989665ffb8d9ce2c7686ad0.zip
Rollup merge of #39888 - nagisa:on-fail-bootstrap, r=alexcrichton
[rustbuild] add a way to run command after failure

This is a simple way to workaround the debugging issues caused by the rustc
wrapper used in the bootstrap process. Namely, it uses some obscure environment
variables and you can't just copy the failed command and run it in the shell or
debugger to examine the failure more closely.

With `--on-fail` its possible to run an arbitrary command within exactly the
same environment under which rustc failed. Theres's multiple ways to use this
new flag:

$ python x.py build --stage=1 --on-fail=env

    would print a list of environment variables and the failed command, so a
    few copy-pastes and you now can run the same rust in your shell outside the
    bootstrap system.

$ python x.py build --stage=1 --on-fail=bash

    Is a more useful variation of the command above in that it launches a whole
    shell with environment already in place! All that's left to do is copy-paste
    the command just above the shell prompt!

Fixes #38686
Fixes #38221
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions