Skip to content

parallel.test-process-finalization is flaky #63056

@IlyasShabi

Description

@IlyasShabi

Test

test-process-finalization

Platform

Windows ARM64

Console output

---
duration_ms: 2182.99
exitcode: 1
severity: fail
stack: |-
  Test failure: 'register is different per thread'
  Location: test\parallel\test-process-finalization.mjs:27:1
  Error: - stdout did not match 'shutdown on worker\nshutdown on main thread\n'
      at TestContext.<anonymous> (file:///d:/workspace/node-test-binary-windows-js-suites/node/test/parallel/test-process-finalization.mjs:28:3)
      at Test.runInAsyncScope (node:async_hooks:226:14)
      at Test.run (node:internal/test_runner/test:1306:25)
      at Test.processPendingSubtests (node:internal/test_runner/test:897:18)
      at Test.postRun (node:internal/test_runner/test:1447:19)
      at Test.run (node:internal/test_runner/test:1372:12)
      at async Test.processPendingSubtests (node:internal/test_runner/test:897:7) {
    options: {
      cwd: 'd:\\workspace\\node-test-binary-windows-js-suites\\node\\test\\fixtures\\process'
    },
    command: 'd:\\workspace\\node-test-binary-windows-js-suites\\node\\Release\\node.exe --expose-gc different-registry-per-thread.mjs'
  }

  [process 7608]: --- stderr ---
  (node:7608) ExperimentalWarning: process.finalization.register is an experimental feature and might change at any time
  (Use `node --trace-warnings ...` to show where the warning was created)
  (node:7608) ExperimentalWarning: process.finalization.register is an experimental feature and might change at any time
  (Use `node --trace-warnings ...` to show where the warning was created)

  [process 7608]: --- stdout ---
  shutdown on worker

  [process 7608]: status = 0, signal = null
  (node:2044) ExperimentalWarning: process.finalization.register is an experimental feature and might change at any time
  (Use `node --trace-warnings ...` to show where the warning was created)
  (node:2044) ExperimentalWarning: process.finalization.registerBeforeExit is an experimental feature and might change at any time
...

Build links

The test has been failing daily since 2026-04-26

Additional information

This may be related to the V8 14.6 update from #61898 which landed shortly before the failures started.

Metadata

Metadata

Assignees

No one assigned

    Labels

    flaky-testIssues and PRs related to the tests with unstable failures on the CI.windowsIssues and PRs related to the Windows platform.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions