[2026] Tracking issue for flaky tests
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.7k
- Forks
- 879
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 68
Description
This is 2026 equivalent of https://github.com/nodejs/undici/issues/3787 where maintainers had reduced flaky tests.
We can use this issue for tracking, and create sub-issues per test failure?
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 reviewing the linked 2025 tracking issue and the current repository test failures; this issue names no specific test, file, or entry point. Break each confirmed flaky failure into a focused sub-issue, with completion defined by resolving or reducing the identified flakiness and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100