TimelyDataflow / TimelyDataflow/timely-dataflow
Multi process tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
There are no tests to make sure timely works correctly for n > 1 cases and this may be an issue sometimes.
For example @utaal recently modified a bit of communication in a fork, and cargo test was ok, but when I tried to run some programs using that forked version of timely, I encountered different problems (crashes & hangs).
This can be avoided by including some tests that verify timely works correctly for n > 1.
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 with the existing test coverage and the cargo test entry point, then identify how to run timely with more than one process. Done means tests exercise n > 1 cases and detect the crashes or hangs described when using a forked version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100