typelevel / typelevel/cats-effect
`IOAppSpec` is flaky again…
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Yay
[error] x warn on cpu starvation
Warning: error] doesn't contain '[WARNING] Your app's responsiveness' (IOAppSpec.scala:213)
This is in GHA. Two consecutive runs, different runners. We probably have to skip this one again. We knew that the integrated runtime stuff would make our particular starvation measurement a bit lossier; that might be what we're seeing here.
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
Inspect IOAppSpec.scala around line 213 and review the GHA failure showing the CPU-starvation warning assertion. Determine how this test has been skipped previously, then apply the same approach if appropriate. Done means the flaky assertion no longer causes CI failures while the surrounding tests still pass.
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
- 42/100