Skip to content

stream: experimental stream/iter implementation #82403

stream: experimental stream/iter implementation

stream: experimental stream/iter implementation #82403

Triggered via pull request March 20, 2026 05:09
Status Failure
Total duration 32m 1s
Artifacts

test-linux.yml

on: pull_request
Matrix: test-linux
Fit to window
Zoom out
Zoom in

Annotations

4 errors, 2 warnings, and 2 notices
test-linux (ubuntu-24.04-arm)
Process completed with exit code 2.
test-linux (ubuntu-24.04-arm): test/parallel/test-fs-promises-file-handle-writer.js#L248
--- stderr --- (node:170887) 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/node/node/node/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/node/node/node/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/node/node/node/test/parallel/test-fs-promises-file-handle-writer.js
test-linux (ubuntu-24.04)
Process completed with exit code 2.
test-linux (ubuntu-24.04): test/parallel/test-fs-promises-file-handle-writer.js#L248
--- stderr --- (node:169863) 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/node/node/node/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/node/node/node/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/node/node/node/test/parallel/test-fs-promises-file-handle-writer.js
test-linux (ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Mozilla-Actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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/
test-linux (ubuntu-24.04)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Mozilla-Actions/sccache-action@7d986dd989559c6ecdb630a3fd2557667be217ad. 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/
sccache stats
72% - 3475 hits, 1385 misses, 0 errors
sccache stats
77% - 3729 hits, 1118 misses, 0 errors