PoolSpec flake
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 39
- Forks
- 18
- Avg merge
- 8h 26m
- Merged PRs (30d)
- 4
Description
On Test (ubuntu-22.04, 3, temurin@8, rootNative) , #631:
==> X org.typelevel.keypool.PoolSpec.Used Resource Cleaned Up By Reaper 6.020s munit.FailException: core/src/test/scala/org/typelevel/keypool/PoolSpec.scala:111 assertion failed
110: later <- pool.state
111: } yield assert(init.total === 1 && later.total === 0)
112: }
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 core/src/test/scala/org/typelevel/keypool/PoolSpec.scala, especially the assertion at line 111, and reproduce the failure in the reported Ubuntu 22.04, Temurin 8, rootNative environment. Trace the test's pool state transitions and determine why the resource count intermittently remains nonzero; done means the test reliably passes and still verifies cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100