Channel used for emitting diagnostic from codegen threads is not guaranteed to be fully drained when compilation session is aborted
Open
Nobody has claimed this yet.
A-testsuite
C-bug
E-needs-investigation
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
AFAIK, the channel used for emitting diagnostic from codegen threads is not guaranteed to be fully drained when compilation session is aborted.
Originally posted by @tmiasko in #82886
This may have lead to e.g. #82886.
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 by tracing the diagnostic channel used by codegen threads and the compilation-session abort path. Determine how diagnostics are drained when an abort occurs, then verify that no diagnostics are lost and add coverage for the aborted-session case if the relevant test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100