-
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
Ensure source file present when calculating max line number #89268
Conversation
In the case where there was a non-dummy span but there was no local file present we would include the line number in the max line number calculation but the sub diagnostic would not be emitted.
r? @davidtwco (rust-highfive has picked a reviewer for you, use r? to override) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bors r+ |
📌 Commit b1e7cbe has been approved by |
⌛ Testing commit b1e7cbe with merge a1c31cfac7538885bbca7dc74cae045e5eae55ec... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Looks like a legitimate failure, I assume |
@bors r- Tests failed, but bors still has it in the merge queue. |
Ping from triage: |
I couldn't figure out why it was failing |
@rossmacarthur any progress on the failure? |
@rossmacarthur @rustbot label: +S-inactive |
Ensure source file present when calculating max line number Resubmission of rust-lang#89268, fixes rust-lang#71363 The behavior difference of `simulate-remapped-rust-src-base` is not something we should take into account here, so limiting targets to run the test makes sense, I think. r? `@davidtwco,` and `@estebank,` you might be interested in this change
In the case where there was a non-dummy span but there was no local file present we would include the line number in the max line number calculation but the sub diagnostic would not be emitted.
Fixes #71363