This found a bug in the test suite!

---- [ui] ui/issues/issue-18075.rs stdout ----
normalized stderr:
warning: some trace filter directives would enable traces that are disabled statically
 | `rustc::middle=debug` would enable the DEBUG level for the `rustc::middle` target
 = note: the static max level is `info`
 = help: to enable DEBUG logging, remove the `max_level_info` feature

Looking at that test, the proposed change makes it useless, and it could just be deleted. I think we should do that.

(#18075 is the issue it was tracking, and that issue looks unlikely to reoccur anyway).

I could change it to rustc_middle=info instead if that helps - that would have effectively the previous behavior but without the warning from tracing.

I don't think that helps personally, the test is just likely no longer useful. We can prune it.

Ok, I removed the unhelpful test.

I think this is good -- @bors r+

That said, it would be great if searching for max_level_info or "some trace filter directives would enable traces that are disabled statically" in CONTRIBUTING.md or rustc-dev-guide would immediately yield results on what to do -- right now that message is likely helpful in the sense that you know you have a problem, but you still don't know what to do to fix it :)

Maybe we could include those two things in the config.toml.example by the debug-logging flag, too, which would make ripgrep in the repository for them yield something useful too.

📌 Commit 8b22d07 has been approved by Mark-Simulacrum

⌛ Testing commit 8b22d07 with merge ccea570...

☀️ Test successful - checks-actions, checks-azure
Approved by: Mark-Simulacrum
Pushing ccea570 to master...