-
Notifications
You must be signed in to change notification settings - Fork 13.4k
More informative diagnotic from x.py test
attempt atop beta checkout
#83172
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
Merged
bors
merged 1 commit into
rust-lang:master
from
pnkfelix:bootstrap-tell-me-what-to-do-about-tidy-on-beta
Mar 16, 2021
Merged
More informative diagnotic from x.py test
attempt atop beta checkout
#83172
bors
merged 1 commit into
rust-lang:master
from
pnkfelix:bootstrap-tell-me-what-to-do-about-tidy-on-beta
Mar 16, 2021
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(rust-highfive has picked a reviewer for you, use r? to override) |
Before:
After:
|
This comment has been minimized.
This comment has been minimized.
oh irony, failing to run the tidy check on this thing that makes it easier to make progress by skipping the tidy check. Oh wait, that's not irony at all. Or rather, its Alanis Morrisette's notion of irony... |
…a 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. (update: placated tidy.)
9400df1
to
d6de60f
Compare
@bors r+ rollup |
📌 Commit d6de60f has been approved by |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Mar 16, 2021
Rollup of 10 pull requests Successful merges: - rust-lang#81822 (Added `try_exists()` method to `std::path::Path`) - rust-lang#83072 (Update `Vec` docs) - rust-lang#83077 (rustdoc: reduce GC work during search) - rust-lang#83091 (Constify `copy` related functions) - rust-lang#83156 (Fall-back to sans-serif if Arial is not available) - rust-lang#83157 (No background for code in portability snippets) - rust-lang#83160 (Deprecate RustcEncodable and RustcDecodable.) - rust-lang#83162 (Specify *.woff2 files as binary) - rust-lang#83172 (More informative diagnotic from `x.py test` attempt atop beta checkout) - rust-lang#83196 (Use delay_span_bug instead of panic in layout_scalar_valid_range) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 branchcurrently fails, and with this change will continue to fail, because
x.py tests
runsx.py test src/tools/tidy
which tries to runrustfmt
and thatwill fail because the
rustfmt
binary is pinned to the current nighlty and wedo 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.