parallel/test-inspector-network-fetch is flaky on Windows

Test

test-inspector-network-fetch

Platform

Windows x64

Console output

---
duration_ms: 475.009
exitcode: 1
severity: fail
stack: |-
  Debugger listening on ws://127.0.0.1:57940/8163745a-9438-419c-9a4c-df0723ddd71e
  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'
  }

  Node.js v25.0.0-pre
...

Build links

• Latest: https://ci.nodejs.org/job/node-test-binary-windows-js-suites/35411/RUN_SUBSET=3,nodes=win2022-COMPILED_BY-vs2022_clang/testReport/junit/(root)/parallel/test_inspector_network_fetch/
• This also has been failing in other forms, see https://github.com/nodejs/reliability/blob/main/reports/2025-07-16.md

Additional information

After the security embargo this has failed most Windows CIs.

The first failure happened in https://github.com/nodejs/node/pull/58077 which seems to be related to the flake itself.

Comienza con test/parallel/test-inspector-network-fetch.js, especialmente con verifyResponseReceived en la línea 112 y su llamador en la línea 148. Reproduce el fallo usando el informe enlazado de Windows CI y, después, compara los fallos relacionados en el informe de fiabilidad y en PR #58077. Se considera completado cuando la prueba pasa de forma consistente en Windows CI sin la respuesta 400 indicada.