`sequential/test-debugger-pid` is flaky on Windows

[inoway46]

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

[inoway46]

This flake has not occurred for the last two days, but I’ll keep monitoring it for a bit longer.

https://github.com/nodejs/reliability/blob/main/reports/2026-05-11.md
https://github.com/nodejs/reliability/blob/main/reports/2026-05-12.md

[inoway46]

Closing this as the flake hasn't reoccurred for a week.

[panva]

This has recurred with the same Windows timeout signature.

I checked the reliability reports from 2026-07-26 through 2026-08-26, deduplicated overlapping report windows by parent Jenkins job, and retained only PRs targeting main. The result is 9 unique PRs / 10 unique CI jobs.

Reports:

• https://github.com/nodejs/reliability/blob/main/reports/2026-08-18.md
• https://github.com/nodejs/reliability/blob/main/reports/2026-08-19.md
• https://github.com/nodejs/reliability/blob/main/reports/2026-08-20.md
• https://github.com/nodejs/reliability/blob/main/reports/2026-08-26.md

All new failures were on the Windows Server 2016 x86 configuration and timed out after approximately 120 seconds:

not ok 1122 sequential/test-debugger-pid
  ---
  duration_ms: 120238.98700
  severity: fail
  exitcode: 1
  stack: |-
    timeout
  ...

The August 26 report also contains one v22.x-staging job; it is excluded from the counts above.

Given the recurrence across unrelated main PRs, this issue should be reopened. The evidence also supports a Windows PASS, FLAKY status entry while the fixed-port/process-leak possibility discussed in #62472 is investigated.