Buggy debuginfo test suite, or just `function-names.rs`?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
In https://github.com/rust-lang/rust/pull/125958 (a PR which changes the way consts are handled in the compiler, and thus alters details like their hashing, etc.) a few lines were trimmed out of a debuginfo test because it was unreasonable to get it to work, despite the function names seemingly being present.
It seems like there might be a bug in the way that the debuginfo test suite handles [...]? Or it might incorrectly treat certain checks as ordering-sensitive, when hashing can change orders? It's unclear, but in any case, undesirable.
This mostly affected the Windows variant of the test.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the debuginfo test suite and the function-names.rs test, then compare its behavior with the Windows variant described in PR 125958. Reproduce the failure and determine whether [...] checks or ordering assumptions cause the missing function-name checks; done means the test suite handles the affected output reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100