Tests should shutdown cudaq-qpud on catastrophic errors
Open
Nobody has claimed this yet.
stale-notified
testing
- Dominant language
- C++
- Stars
- 1.1k
- Forks
- 456
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 165
Description
Some of the target tests (/targettests) run using cudaq-qpud.
When the executable crashes (say with a SIGSEGV), these tests do not shutdown the running cudaq-qpud daemon. This can lead to llvm-lit waiting for manual intervention or a system timeout to end.
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 in /targettests and inspect how tests launch and clean up cudaq-qpud under llvm-lit. Reproduce a catastrophic executable failure, then trace the existing shutdown path; done means the daemon is terminated automatically and llvm-lit no longer waits for manual intervention or a system timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100