-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Add more diagnostic items #96302
Add more diagnostic items #96302
Conversation
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
I think it's hitting this: rust/compiler/rustc_trait_selection/src/traits/error_reporting/mod.rs Lines 1834 to 1840 in 0b3404b
|
r? @Manishearth |
📌 Commit ea013e0 has been approved by |
…=Manishearth Add more diagnostic items This just adds a handful diagnostic items I noticed were missing. Would it be worth doing this for all of the remaining types? I'm willing to do it if it'd be helpful.
…=Manishearth Add more diagnostic items This just adds a handful diagnostic items I noticed were missing. Would it be worth doing this for all of the remaining types? I'm willing to do it if it'd be helpful.
Ci isn't happy. @bors: r- |
Here's why CI is failing: #96302 (comment). It shouldn't be interfering with tests, so I'm not sure what's going on here. |
Not sure either, @estebank? |
Oh! So that's a very crude filter to avoid verbose output, relying on the assumption that if something is a diagnostic item there are better things than list them in those errors. Can you do In the past I've added diagnostic items on an as-needed basis, though (as they can be safely added in the same commit as the change that uses them). |
ea013e0
to
a235c1d
Compare
I'm confused. Over 700 files were modified, and most of these changes don't even look remotely related to what's been added. The only diagnostic item I needed is causing so many problems 😄 |
Try pulling a more recent master and rebasing your changes on top of it, I'm noticing some output changes caused by a relatively recently landed PR. |
c9bf370
to
a1e0cfa
Compare
Oops, I blindly added |
I'm as baffled as you are 😮 @bors retry lets check it's not spurious |
…=manishearth Add more diagnostic items This just adds a handful diagnostic items I noticed were missing. Would it be worth doing this for all of the remaining types? I'm willing to do it if it'd be helpful.
…=manishearth Add more diagnostic items This just adds a handful diagnostic items I noticed were missing. Would it be worth doing this for all of the remaining types? I'm willing to do it if it'd be helpful.
failed in rollup |
@bors r- |
a1e0cfa
to
be9dd2d
Compare
Looks like the failing test just had a windows only version added. Hopefully that's the last issue with this 😄 |
@bors r=manishearth rollup=never |
I'm guessing bors is stuck @bors ping |
😪 I'm awake I'm awake |
📌 Commit be9dd2d has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (6846164): comparison url. Summary:
If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression Footnotes |
This just adds a handful diagnostic items I noticed were missing.
Would it be worth doing this for all of the remaining types? I'm willing to do it if it'd be helpful.