-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Update rustc-guide #67940
Update rustc-guide #67940
Conversation
This is submodule-only. |
📌 Commit 2aa6457149e87d12e081b6ec6ad35f0dc860305a has been approved by |
Needs more link fix, out of the queue for now. |
2aa6457
to
e65cbc8
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
e65cbc8
to
ab77318
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
ab77318
to
6e76873
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
6e76873
to
6421127
Compare
Okay, it should be fine... |
📌 Commit 6421127 has been approved by |
Update rustc-guide r? @ghost CC: @rust-lang/wg-learning
Update rustc-guide r? @ghost CC: @rust-lang/wg-learning
@bors retry rolled up IMO this shouldn't be rollup=never, since it seems low-risk once it's passing smoke tests. |
@tmandry We did this in the past, but spurious failures tended to cause rollup failures, so we adopted a policy of not rolling up rustc-guide update. This is part of the reason why WG-learning makes its own PRs to update the guide, rather than ehuss doing it with their regular round of book/doc updates. |
Okay, good to know. Can you elaborate on what kind of spurious failures tend to happen? |
Yes, or some link breaks over night while the PR is in the queue, as happened at the top of this PR. |
Got it, thanks. I know this isn't really the place for this discussion, but it seems reasonable to me to leave the link checks for smoke tests and not put those in CI. |
Not sure what others think, but I'm open to suggestions. The main thing is that it is helpful for rustc-guide to be tracked by toolstate. |
Update rustc-guide r? @ghost CC: @rust-lang/wg-learning
☀️ Test successful - checks-azure |
📣 Toolstate changed by #67940! Tested on commit fb4ac14. 🎉 rustc-guide on linux: test-fail → test-pass (cc @JohnTitor @amanjeev @spastorino @mark-i-m, @rust-lang/infra). |
Tested on commit rust-lang/rust@fb4ac14. Direct link to PR: <rust-lang/rust#67940> 🎉 rustc-guide on linux: test-fail → test-pass (cc @JohnTitor @amanjeev @spastorino @mark-i-m, @rust-lang/infra).
r? @ghost
CC: @rust-lang/wg-learning