Process completed with exit code 2.

--- stderr --- (node:52885) ExperimentalWarning: stream/iter is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created) node:internal/process/promises:332 triggerUncaughtException(err, true /* fromPromise */); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: + actual - expected Comparison { message: 'Invalid state: The writer is closed', + name: 'TypeError' - name: 'Error' } at async testWriteAfterEndRejects (/home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:3) at async Promise.all (index 11) { generatedMessage: true, code: 'ERR_ASSERTION', actual: TypeError [ERR_INVALID_STATE]: Invalid state: The writer is closed at Object.write (node:internal/fs/promises:652:13) at testWriteAfterEndRejects (/home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:26) at async Promise.all (index 11) { code: 'ERR_INVALID_STATE' }, expected: { name: 'Error', message: /closed/ }, operator: 'rejects', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node --experimental-stream-iter /home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js

Process completed with exit code 2.

--- stderr --- (node:28746) ExperimentalWarning: stream/iter is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created) node:internal/process/promises:332 triggerUncaughtException(err, true /* fromPromise */); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: + actual - expected Comparison { message: 'Invalid state: The writer is closed', + name: 'TypeError' - name: 'Error' } at async testWriteAfterEndRejects (/Users/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:3) at async Promise.all (index 11) { generatedMessage: true, code: 'ERR_ASSERTION', actual: TypeError [ERR_INVALID_STATE]: Invalid state: The writer is closed at Object.write (node:internal/fs/promises:652:13) at testWriteAfterEndRejects (/Users/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:26) at async Promise.all (index 11) { code: 'ERR_INVALID_STATE' }, expected: { name: 'Error', message: /closed/ }, operator: 'rejects', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node --experimental-stream-iter /Users/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js

Process completed with exit code 2.

--- stderr --- (node:51322) ExperimentalWarning: stream/iter is an experimental feature and might change at any time (Use `node --trace-warnings ...` to show where the warning was created) node:internal/process/promises:332 triggerUncaughtException(err, true /* fromPromise */); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: + actual - expected Comparison { message: 'Invalid state: The writer is closed', + name: 'TypeError' - name: 'Error' } at async testWriteAfterEndRejects (/home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:3) at async Promise.all (index 11) { generatedMessage: true, code: 'ERR_ASSERTION', actual: TypeError [ERR_INVALID_STATE]: Invalid state: The writer is closed at Object.write (node:internal/fs/promises:652:13) at testWriteAfterEndRejects (/home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js:248:26) at async Promise.all (index 11) { code: 'ERR_INVALID_STATE' }, expected: { name: 'Error', message: /closed/ }, operator: 'rejects', diff: 'simple' } Node.js v26.0.0-pre Command: out/Release/node --experimental-stream-iter /home/runner/work/_temp/node-v26.0.0-nightly2026-03-206eb87bdf92-slim/test/parallel/test-fs-promises-file-handle-writer.js

Canceling since a higher priority waiting request for Test Shared libraries-jasnell/new-streams-prototype exists

The operation was canceled.

Canceling since a higher priority waiting request for Test Shared libraries-jasnell/new-streams-prototype exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cachix/cachix-action@3ba601ff5bbb07c7220846facfa2cd81eeee15a1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/