diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-11-05 10:32:44 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-05 10:32:44 +0900 |
| commit | 6964ec2f72c500bb5577cbe4f9d5c34372223a12 (patch) | |
| tree | f00ce59c800e63378730d86638f3da963eacde37 /compiler/rustc_mir_transform/src/coverage/counters.rs | |
| parent | a5802d073105c4026af1dad4d315eed56e91352c (diff) | |
| parent | 9057936a9aba6b85a3de119d061c7a7168f60ce8 (diff) | |
| download | rust-6964ec2f72c500bb5577cbe4f9d5c34372223a12.tar.gz rust-6964ec2f72c500bb5577cbe4f9d5c34372223a12.zip | |
Rollup merge of #90544 - ehuss:demote-locator-warn, r=petrochenkov
Demote metadata load warning to "info". There is a warn log message for whenever the crate loader fails to load metadata from a candidate file. I think this warning is too aggressive, as there are several situations where metadata information might not be found in a candidate file, which is normal. Also, this warning is somewhat confusing, and non-actionable in most cases for a user (most users will not know what it means). If the crate loader ultimately does not find a valid crate, then an error will be reported (and hopefully #88368 will improve that error message). If a rustc developer wants to debug a loader problem, they can still use `RUSTC_LOG=rustc_metadata=debug` and get the details. There is more discussion of this particular warning at https://github.com/rust-lang/rust/issues/89795#issuecomment-940798190. Fixes #90525
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/counters.rs')
0 files changed, 0 insertions, 0 deletions