typelevel / typelevel/cats-effect
`IOAppSpec` starvation test is a bit flaky
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
[error] x warn on cpu starvation
Warning: error] doesn't contain '[WARNING] Your app's responsiveness' (IOAppSpec.scala:211)
I think we just cut off stderr a bit too early.
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 IOAppSpec.scala around line 211 and inspect how the starvation test captures stderr and determines when to stop reading it. Run the “warn on cpu starvation” test and adjust the cutoff so the responsiveness warning is observed reliably; done means the test passes without intermittent missing-warning failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100