Add syscall-interruption checkpointing tests
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Followup to #1139. These are tricky because the pexpect script has to deal with gdb entering signal-stop when the tests kill themselves.
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 reading issue #1139 and locate the pexpect-based tests for syscall-interruption checkpointing. Reproduce the existing test flow and inspect how gdb handles signal-stop when the tests terminate themselves. Done means the added tests reliably cover syscall-interruption checkpointing without failing on that signal-stop state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- operating-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100