Skip to content

test-blob-slice-with-large-size is flaky #57235

Description

@aduh95

Test

test-blob-slice-with-large-size

Platform

SmartOS

Console output

---
duration_ms: 290.507
exitcode: 1
severity: fail
stack: |-
  /home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos23-x64/test/pummel/test-blob-slice-with-large-size.js:18
      throw e;
      ^

  RangeError: Array buffer allocation failed
      at new ArrayBuffer (<anonymous>)
      at new Uint8Array (<anonymous>)
      at new FastBuffer (node:internal/buffer:961:5)
      at createUnsafeBuffer (node:internal/buffer:1097:12)
      at allocate (node:buffer:445:10)
      at Function.allocUnsafe (node:buffer:410:10)
      at Object.<anonymous> (/home/iojs/build/workspace/node-test-commit-smartos/nodes/smartos23-x64/test/pummel/test-blob-slice-with-large-size.js:12:22)
      at Module._compile (node:internal/modules/cjs/loader:1734:14)
      at Object..js (node:internal/modules/cjs/loader:1899:10)
      at Module.load (node:internal/modules/cjs/loader:1469:32)

  Node.js v24.0.0-pre

Build links

Additional information

It seems to reproduce quite rarely

Activity

  1. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on Feb 28, 2025
  2. aduh95 commented on Feb 28, 2025

    @aduh95
    ContributorAuthor

    /cc @nodejs/platform-smartos

  3. joyeecheung commented on May 18, 2025

    @joyeecheung
    Member

    This is now flaking many Windows tests and somehow it's relatively recent (starting from May 16 -perhaps something landed around that time made it a lot more flaky). In the latest report https://github.com/nodejs/reliability/blob/main/reports/2025-05-18.md this has failed 17 PRs out of the last 100 CI runs

  4. added
    windowsIssues and PRs related to the Windows platform.
    on May 21, 2025
  5. tniessen commented on May 21, 2025

    @tniessen
    Member

    In #58379, this test has failed 6 of 8 Windows CI runs and is still blocking the PR.

  6. joyeecheung commented on May 21, 2025

    @joyeecheung
    Member

    I think it's just the test not being written in a way that's robust enough to skip when there's not enough memory. Fix in #58414

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.smartosIssues and PRs related to the SmartOS platform.windowsIssues and PRs related to the Windows platform.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions