microsoft / microsoft/demikernel
[test] Close sockets and clean up on error for integration testing
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Description
Description
Currently, our integration tests in tests/rust do not clean up on error. This may leave the OS in a bad state and makes it impossible to continue running experiments on failure.
How to Reproduce
Steps to reproduce the behavior:
- Run any unit test in tests/rust
- Hit an error (e.g., unable to bind)
- Dangling socket that isn't properly closed
Expected Behavior
All clean up should be done on error instead of just exiting.
Related Issues
#207
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 tests/rust and run a unit test while reproducing an error such as an inability to bind. Trace the integration-test error path and identify where sockets remain open. Done means error handling closes the sockets and cleanup allows later experiments to run without dangling resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100