Uh oh!
There was an error while loading. Please reload this page.
Remove FIXME since there is nothing to be fixed - #89907
Conversation
jyn514
left a comment
There was a problem hiding this comment.
Haven't looked at the test case, but the abort_if_errors() call looks right.
camelid
commented
Oct 15, 2021
What does this mean? Do you mean that if there was a rustc error, no rustdoc errors will be reported until the rustc error is fixed? |
GuillaumeGomez
commented
Oct 15, 2021
Exactly. For example, in the test I splitted in two parts, it's because the rustdoc lints weren't emitted because we aborted before them. |
Mark-Simulacrum
commented
Oct 15, 2021
rustc itself generally deduplicates errors, that's just turned off for UI tests. Does this duplication reproduce outside of UI tests? If not, it may be preferable to avoid the early abort, which we're generally trying to move away from where possible. |
There was a problem hiding this comment.
| tcx.sess.abort_if_errors(); | |
| // Avoid emitting duplicate errors later on. | |
| tcx.sess.abort_if_errors(); |
There was a problem hiding this comment.
I think this is unrelated to this change, but why did it not emit missing_docs for the crate before?
Seems like the situation is this:
Before
- function
After
- crate
- function
There was a problem hiding this comment.
The rustc lint passes come afterwards (unless I missed something?).
camelid
commented
Oct 15, 2021
Huh, you're right; it doesn't seem to reproduce outside of UI tests. I thought I had found it "in the wild", but perhaps not. |
camelid
commented
Oct 15, 2021
I guess this PR and associated issue can be closed then? |
camelid
commented
Oct 15, 2021
Or maybe just repurpose this PR so it removes the FIXME in the test. |
GuillaumeGomez
commented
Oct 15, 2021
As you prefer. I personally don't have preference here. Just like the borrow checker comes after the other checks, I don't see it abnormal to have the rustdoc checks only if rustc is happy. |
It'd be better to have as many errors as possible be reported in one build, as long as none are spurious. So I don't see why we should add this early abort, especially if T-compiler (or whichever team Mark was referring to) is moving away from it. The borrow checker not running if earlier stages failed is just a technical limitation IIUC. |
GuillaumeGomez
commented
Oct 15, 2021
Then I'll update the PR to remove the FIXME. :) |
94ff696 to
8d9dbf7CompareGuillaumeGomez
commented
Oct 15, 2021
And done! |
camelid
commented
Oct 16, 2021
r=me with the commit message amended to include something like this:
|
The errors are deduplicated when displayed to users. They only appear multiple times in UI tests.
8d9dbf7 to
7bad85eCompareGuillaumeGomez
commented
Oct 16, 2021
Done! |
camelid
commented
Oct 16, 2021
Thanks! @bors r+ rollup |
bors
commented
Oct 16, 2021
📌 Commit 7bad85e has been approved by |
629ec2a to
7bad85eComparecamelid
commented
Oct 16, 2021
@bors r+ |
bors
commented
Oct 16, 2021
📌 Commit 7bad85e has been approved by |
…s, r=camelid Remove FIXME since there is nothing to be fixed Resolvesrust-lang#88593. The errors are deduplicated when displayed to users. They only appear multiple times in UI tests. cc `@jyn514` r? `@camelid`
Rollup of 7 pull requests Successful merges: - rust-lang#89507 (Add `#[repr(i8)]` to `Ordering`) - rust-lang#89849 (CI: Selecting the Xcode version no longer needed with the macos-11 runners.) - rust-lang#89886 (Update the wasi-libc built with the wasm32-wasi target) - rust-lang#89907 (Remove FIXME since there is nothing to be fixed) - rust-lang#89943 (clippy::complexity fixes) - rust-lang#89953 (Make Option::as_mut const) - rust-lang#89958 (Correct small typo) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Resolves#88593.
The errors are deduplicated when displayed to users. They only appear
multiple times in UI tests.
cc @jyn514
r? @camelid