typelevel / typelevel/cats-effect
`WorkerThreadNameSpec` seems a bit flaky in CI
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
[info] WorkerThread should
[error] x rename itself when entering and exiting blocking region
[error] blocker thread not found after reset (WorkerThreadNameSpec.scala:84)
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 by inspecting WorkerThreadNameSpec.scala at line 84 and reproduce the failing “rename itself when entering and exiting blocking region” test in CI or locally. Trace the blocker-thread reset and determine what makes the test flaky; done means the spec passes reliably without weakening its assertion.
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
- 30/100