haskell-distributed / haskell-distributed/distributed-process
Test concurrency
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
At a minimum, the TCP transport has a few threads on a couple of nodes which all need to be coordinated to work as expected.
n-t-tcp currently lacks the ability to test different schedules of these threads and ensure that all of them satisfy the properties in tests.
We need to enhance the tests to allow for this. Choose an existing solution for testing concurrency or develop one. Most likely, the code will need to be instrumented or refactored for this sake.
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 examining the n-t-tcp tests and the TCP transport's coordinated threads. Determine whether an existing concurrency-testing solution can exercise different thread schedules; done means the tests cover those schedules and verify that all stated properties hold.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100