-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Improve error display for codeblocks in rustdoc #53933
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
Improve error display for codeblocks in rustdoc #53933
Conversation
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 |
|
Also, can you add a test? Maybe try to reduce some of the linked issue's bindgen output into something we can stuff into a |
Oh damn, forgot to add the test! |
97ac9ae
to
f14a145
Compare
CI passed and forgotten test added. |
Ping from triage @QuietMisdreavus: This PR requires your review. |
Whoops, sorry for letting this one slip! @bors r+ |
📌 Commit f14a14535976e13938cae6442053201adee3bcb2 has been approved by |
@bors r- In this test from cargo, the exit code becomes 0 instead of 101. See #54168 (comment). |
This is... weird... I suppose the stderr isn't checked the same way or something along the line. I'll fix it in the next days. |
I think Cargo is expecting this test to crash rustdoc; does this PR make parse errors non-fatal? |
It does indeed. That was the whole point of the PR, which is why I'm having trouble in here. Should I disable the test on cargo waiting for this PR to get merged? |
@rust-lang/cargo Should I open a PR on cargo to disable the failing test before merging this one (and then fixing the test on cargo)? |
Either that or updating the test to only verify the output and not the exit code should be fine, yeah. |
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 |
@rust-lang/infra Is this a known error? |
Seems like a spurious failure while uploading artifacts to S3. @bors retry |
⌛ Testing commit 322e469 with merge 13187c545947d3711a173cc472e00344dfdca5b4... |
💔 Test failed - status-travis |
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 |
@bors retry S3 deploy error again |
⌛ Testing commit 322e469 with merge 794ee371e552644933c2ab037253f1befdf7391f... |
💔 Test failed - status-travis |
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 |
@bors: retry |
…tMisdreavus Improve error display for codeblocks in rustdoc Part of #53919. r? @QuietMisdreavus
☀️ Test successful - status-appveyor, status-travis |
Part of #53919.
r? @QuietMisdreavus