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 #58077 which seems to be related to the flake itself.

test: mark test-inspector-network-fetch as flaky on Windows

test: make test-inspector-network-resource sequential

test: mark test-inspector-network-fetch as flaky on Windows

test: make test-inspector-network-resource sequential

Still flaky in the CI: https://github.com/nodejs/reliability/blob/main/reports/2025-08-26.md

Reason	`parallel/test-inspector-network-fetch`
Type	JS_TEST_FAILURE
Failed PR	13 (https://github.com/nodejs/node/pull/59567/, https://github.com/nodejs/node/pull/59570/, https://github.com/nodejs/node/pull/59350/, https://github.com/nodejs/node/pull/59579/, https://github.com/nodejs/node/pull/59595/, https://github.com/nodejs/node/pull/58155/, https://github.com/nodejs/node/pull/59283/, https://github.com/nodejs/node/pull/58680/, https://github.com/nodejs/node/pull/59601/, https://github.com/nodejs/node/pull/59616/, https://github.com/nodejs/node/pull/59602/, https://github.com/nodejs/node/pull/59179/, https://github.com/nodejs/node/pull/59603/)
Appeared	test-rackspace-win2019_vs2019-x64-2, test-rackspace-win2022_vs2022-x64-5, test-rackspace-win2022_vs2022-x64-2, test-rackspace-win2019_vs2019-x64-3, test-rackspace-win2022_vs2022-x64-3, test-rackspace-win2022_vs2022-x64-1, test-rackspace-win2019_vs2019-x64-1
First CI	https://ci.nodejs.org/job/node-test-pull-request/68781/
Last CI	https://ci.nodejs.org/job/node-test-pull-request/68867/

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
  ...

test: mark test-inspector-network-fetch as flaky again

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.

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.

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: deflake inspector network fetch

Navigation Menu

Repository navigation

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

Test

Platform

Console output

Build links

Additional information

3 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

Test

Platform

Console output

Build links

Additional information

Activity

joyeecheung commented on Aug 26, 2025

targos commented on Aug 27, 2025

targos commented on Aug 27, 2025

targos commented on Aug 27, 2025

3 remaining items

github-actions commented on Apr 19, 2026

github-actions commented on May 19, 2026

lpinca commented on Aug 26, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions