Skip to content

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

Description

@joyeecheung

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

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.

Activity

added
flaky-testIssues and PRs involving tests that fail intermittently in CI.
on Jul 16, 2025

joyeecheung commented on Aug 26, 2025

@joyeecheung
MemberAuthor

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

targos commented on Aug 27, 2025

@targos
Member

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.

targos commented on Aug 27, 2025

@targos
Member

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.

targos commented on Aug 27, 2025

@targos
Member

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

@github-actions
Contributor

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.

added
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Apr 19, 2026

github-actions commented on May 19, 2026

@github-actions
Contributor

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.

reopened this on Aug 26, 2026

lpinca commented on Aug 26, 2026

@lpinca
Member

I think issues with the flaky-test label should not be closed for inactivity.

added
never-staleIssues and PRs exempt from automated stale handling.
and removed
staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Aug 26, 2026
added a commit that references this issue on Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs involving tests that fail intermittently in CI.never-staleIssues and PRs exempt from automated stale handling.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions