Tracking issue for MCP 1012: Stabilizing the state of the debuginfo test suite

This is a tracking issue for MCP "Stabilizing the state of the debuginfo test suite" (rust-lang/compiler-team#1012).

[!NOTE]
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.

A tracking issue is however not meant for large scale discussion, questions, or bug reports.
Instead, open a dedicated issue for the specific matter, link to this tracking issue and ping the MCP author.
Alternatively, post in the Zulip stream linked from the MCP.

Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Implementation history

• https://github.com/rust-lang/rust/pull/159455
• https://github.com/rust-lang/rust/pull/159451
• https://github.com/rust-lang/rust/pull/159177

Unresolved questions

None so far.

Change announcements

Follow #t-infra/bootstrap/announcements > Various debuginfo test infra changes.

Discussions

• See backlinks on rust-lang/compiler-team#1012
• #t-compiler/major changes > Stabilizing the state of the debuginfo t… compiler-team#1012

@jieyouxu, consider @rustbot claim'ing the work.

Start by reading compiler-team#1012 and the implementation history in PRs 159455, 159451, and 159177. Follow the linked discussions and announcement for the debuginfo test-suite changes; the tracking work is complete when the MCP's overall implementation progress and remaining questions are resolved.