Fix flaky test
Open
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 292
- Forks
- 80
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
> There, just a retry and this is green, we've got a flaky test @elbrujohalcon 🤷🏽
Originally posted by @elbrujohalcon in https://github.com/inaka/worker_pool/issues/199#issuecomment-1862386973
Contributor guide
No contributing guide indexed for this repository
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
Read issue #199 and its referenced comment first; this issue names no test file or entry point. Locate the flaky test described there, reproduce the failure, and confirm it passes reliably without relying on a retry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100