microsoft / microsoft/demikernel
[test] Run each test suite in new process
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 151
- PR merge metrics
- No merged PRs in 30d
Description
Context
Currently we run all of our integration tests sequentially in a single process. This can make it difficult to isolate errors from one test to another, so we end up commenting out the tests that we do not want to run when debugging.
Proposed Solution
Launch the test suite in each directory of tests/rusts/*. For example, we would run 6 tests in tcp-tests in 6 processes. The tests should run sequentially, so we wait for the process to finish before launching the next one.
Alternative Solutions
We could just restart the libOS, however, DPDK does not have a clean up function that lets us restart it. Thus if one of the tests leaves DPDK in a bad state, it is difficult to isolate the issue.
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 locating the integration-test entry point that discovers suites under tests/rusts/*. Read how the current runner launches tests and confirm the directory layout and process behavior. Done means each suite runs in its own process, suites remain sequential, and failures can be isolated without commenting out unrelated tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100