Add a time or disk-space cap to rr
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I think I recorded this bug, but I was off playing my fiddle and didn't notice until too late. The test appeared to livelock or something like that and kept generating events until I ran out of disk space.
For unattended infra, this would be a bad problem. Similarly, if the test had deadlocked, it would have been nice for rr to time out after a while with an error message.
@rocallahan not sure how you feel about this for 1.0. My inclination is to punt.
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 reproducing the unattended recording scenario described in the issue, including runaway event generation and a deadlock. The issue does not name files, tests, or entry points; first identify where recording detects errors and how it reports them. Done would require an agreed time or disk-space limit with a clear error outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100