Repository navigation
parallel/test-inspector-network-fetch is flaky on Windows #59090
Description
Activity
Still flaky in the CI: https://github.com/nodejs/reliability/blob/main/reports/2025-08-26.md
Example
not ok 598 parallel/test-inspector-network-fetch
---
duration_ms: 443.96300
severity: fail
exitcode: 1
stack: |-
Debugger listening on ws://127.0.0.1:58677/62a548b4-800d-4258-a362-7b1d24053ed2
For help, see: https://nodejs.org/en/docs/inspector
node:internal/process/promises:332
triggerUncaughtException(err, true /* fromPromise */);
^
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
400 !== 200
at verifyResponseReceived (C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-inspector-network-fetch.js:112:10)
at C:\workspace\node-test-binary-windows-js-suites\node\test\parallel\test-inspector-network-fetch.js:148:24
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
generatedMessage: true,
code: 'ERR_ASSERTION',
actual: 400,
expected: 200,
operator: 'strictEqual',
diff: 'simple'
}
Node.js v25.0.0-pre
...
I'm unable to reproduce on my Windows machine:
> python tools/test.py --parallel=64 --repeat=1024 --mode=debug parallel/test-inspector-network-fetch.js
[01:02|% 100|+ 1024|- 0]: Done
All tests passed.
I see #59104 in the timeline. Was it a mistake? It moved test-inspector-network-resource.js to sequential but removed test-inspector-network-fetch.js from flaky.
Also, it doesn't look flaky to me, just broken. In #59518, it failed 6 times in a row.
3 remaining items
github-actions commented on Apr 19, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commented on May 19, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
I think issues with the flaky-test label should not be closed for inactivity.
Test
test-inspector-network-fetch
Platform
Windows x64
Console output
Build links
Additional information
After the security embargo this has failed most Windows CIs.
The first failure happened in #58077 which seems to be related to the flake itself.