Intermittent test failure in record_replay test
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
I'm seeing about 3% failure rate in any of the record_replay tests, failing with the following assertion:
[FATAL /home/keno/rr/src/RecordTask.cc:219:~RecordTask()]
(task 1976525 (rec:1976525) at time 204112)
-> Assertion `stable_exit' failed to hold. PTRACE_O_TRACEEXIT only supported for stable exits for now
I haven't been running rr tests enough recently to say when this was introduced, but the test was stable a few months ago when I last did an extensive testing run.
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 running the record_replay tests and reproducing the intermittent assertion reported at src/RecordTask.cc:219. Inspect the stable_exit failure and the surrounding RecordTask shutdown path, then identify the cause of the instability. Done means the affected tests no longer fail intermittently and the regression is covered by the test suite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100