Tracking Issue for debuginfo testsuite test infra woes #134682
Labels
A-compiletest
Area: The compiletest test runner
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-test-infra
Area: test infrastructure (may span bootstrap/compiletest/more)
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-infra
Relevant to the infrastructure team, which will review and decide on the PR/issue.
This is a tracking issue for various problems and deficiencies related to the
debuginfo
test suite located attests/debuginfo
, mostly on the test-infra side (and not compiler bugs).Environment control
Test coverage issues
Build/bootstrap issues
./x test tests/debuginfo
triggers recompiles for debugger visualizer script changes #133692--lldb-python
path #69869compiletest issues
External issues
LLDB
ModuleNotFoundError: No module named '_lldb'
with BuildType=Debug on Windows llvm/llvm-project#87381GDB
rustc
failed to passdebuginfo
testsuite when using GDB 15 #122751MSVC
Unknown, needs investigation
These bugs may need investigation (is it our compiler bug, our test infra bug, external bug, or a combination of both?).
function-names.rs
? #126060 (maybe in debuginfo we emit?)arm-android
#74847 (arm-android
, good luck trying to repro this locally)Possible test infra cleanups/improvements
The text was updated successfully, but these errors were encountered: