about summary refs log tree commit diff
path: root/library/std/src/sys/unix/stack_overflow.rs
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2021-03-16 23:54:02 +0900
committerGitHub <noreply@github.com>2021-03-16 23:54:02 +0900
commitb62997fd2478999cdf3439024576052d22a5e983 (patch)
tree805dbfef341f6f82c9744796f7532c45e379e518 /library/std/src/sys/unix/stack_overflow.rs
parent70bacd67273b09dba850f51c910b5214aa7f2cd3 (diff)
parentd6de60fb322828ec3b828278f05598f2db282142 (diff)
downloadrust-b62997fd2478999cdf3439024576052d22a5e983.tar.gz
rust-b62997fd2478999cdf3439024576052d22a5e983.zip
Rollup merge of #83172 - pnkfelix:bootstrap-tell-me-what-to-do-about-tidy-on-beta, r=Mark-Simulacrum
More informative diagnotic from `x.py test` attempt atop beta checkout

Make bootstrap be more informative when one does `x.py test` on a beta checkout without other mods.

To be clear, by default running `x.py test` on a checkout of the beta branch
currently fails, and with this change will continue to fail, because `x.py
tests` runs `x.py test src/tools/tidy` which tries to run `rustfmt` and that
will fail because the `rustfmt` binary is pinned to the current nighlty and we
do not attempt to distribute one for the beta builds.

This change gives a better error message than the current message, which is just
"./x.py fmt is not supported on this channel" without providing any hint about
what one might do about that problem.
Diffstat (limited to 'library/std/src/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions