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

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