-
-
Notifications
You must be signed in to change notification settings - Fork 15.6k
Tracking issue for MCP 1012: Stabilizing the state of the debuginfo test suite #159635
Copy link
Copy link
Open
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerA-debuggersArea: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)Area: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)A-debuggers-cdbArea: cdbArea: cdbA-debuggers-gdbArea: gdbArea: gdbA-debuggers-lldbArea: lldbArea: lldbA-debuginfoArea: Debugging information in compiled programs (DWARF, PDB, etc.)Area: Debugging information in compiled programs (DWARF, PDB, etc.)A-test-infraArea: test infrastructure (may span bootstrap/compiletest/more)Area: test infrastructure (may span bootstrap/compiletest/more)A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcB-MCP-approvedBlocker: Approved by an accepted MCP but not yet fully implemented.Blocker: Approved by an accepted MCP but not yet fully implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Activity
Metadata
Metadata
Assignees
Labels
A-compiletestArea: The compiletest test runnerArea: The compiletest test runnerA-debuggersArea: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)Area: debuggers themselves (gdc, lldb, cdb, WinDbg, etc.)A-debuggers-cdbArea: cdbArea: cdbA-debuggers-gdbArea: gdbArea: gdbA-debuggers-lldbArea: lldbArea: lldbA-debuginfoArea: Debugging information in compiled programs (DWARF, PDB, etc.)Area: Debugging information in compiled programs (DWARF, PDB, etc.)A-test-infraArea: test infrastructure (may span bootstrap/compiletest/more)Area: test infrastructure (may span bootstrap/compiletest/more)A-testsuiteArea: The testsuite used to check the correctness of rustcArea: The testsuite used to check the correctness of rustcB-MCP-approvedBlocker: Approved by an accepted MCP but not yet fully implemented.Blocker: Approved by an accepted MCP but not yet fully implemented.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
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
Unresolved questions
None so far.
Change announcements
Follow #t-infra/bootstrap/announcements > Various debuginfo test infra changes.
Discussions
@jieyouxu, consider
@rustbot claim'ing the work.