Add futurelock tests
Open
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 59
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 15
Description
Ref Dylan's comment: https://github.com/awslabs/shuttle/pull/217#issuecomment-3475205173,
we should add futurelock tests [rfd.shared.oxide.computer/rfd/0609](https://rfd.shared.oxide.computer/rfd/0609).
Punting on this for now in part because I want to use `shuttle_tokio::select!` for some of the tests, and in part because I want to spend a bit of time exploring futurelocks and time models
Contributor guide
Research direction
Start by reading the linked RFD 0609 and Dylan's comment on pull request 217 to identify the futurelock cases to cover. Explore futurelocks and time models in Shuttle, then determine how shuttle_tokio::select! should be used in the tests. Done means the identified futurelock scenarios are covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100