testmycode / testmycode/tmc-server
Interrupting tests may leave stuff running
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
Description
Sometimes interrupting a test run with Control+C leaves services in the background. The "root helper" subprocess doesn't seem to receive SIGINT reliably. Sometimes it receives it twice IIRC.
Also, the root helper is interrupted on the first control+c which only causes rspec to wait for the current test to finish. This is likely to cause the current test to fail in a misleading way.
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 how the root helper subprocess is launched and how RSpec handles Control+C; the issue does not name specific files or tests. Reproduce an interrupted test run, then verify that the helper receives SIGINT reliably, is not signaled twice, and that the first interrupt does not misleadingly fail the current test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100