`sequential/test-debugger-pid` is flaky on Windows
Open
Nobody has claimed this yet.
flaky-test
never-stale
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Test
sequential/test-debugger-pid
Platform
Windows x64
Console output
not ok 994 sequential/test-debugger-pid
---
duration_ms: 120195.85000
severity: fail
exitcode: 1
stack: |-
timeout
...
Build links
- https://github.com/nodejs/reliability/blob/main/reports/2026-05-07.md
- https://github.com/nodejs/reliability/blob/main/reports/2026-05-08.md
- https://github.com/nodejs/reliability/blob/main/reports/2026-05-09.md
Additional information
No response
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 sequential/test-debugger-pid test and the linked reliability reports for the Windows x64 timeout pattern. Run the test on Windows and compare its behavior with other platforms. Done means identifying and fixing the flakiness so the test completes reliably without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100