We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test-fs-cp
If you don’t already have one, then make a local clone of the nodejs/node repo by running this command:
nodejs/node
git clone https://github.com/nodejs/node
Change directory into your clone of the node repo by running this command:
node
cd <path-to-node-repo>
(Recommended) Switch to a Git commit where this problem is know to occur by running this command:
git switch --detach b0c65bbe8aef0c1b17bdbbb45f6a03210309134d
Build Node.js from source by following these instructions.
Run Node.js’s test-fs-cp test by running this command:
out/Release/node test/parallel/test-fs-cp.mjs
When I try following the steps to reproduce on a bcachefs filesystem, the last command prints this…
node:internal/modules/run_main:104 triggerUncaughtException( ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal: + actual - expected Comparison { + code: 'ENOENT' - code: 'ERR_FS_CP_SOCKET' } at file:///home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/parallel/test-fs-cp.mjs:380:10 at ModuleJob.run (node:internal/modules/esm/module_job:272:25) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:580:26) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:98:5) { generatedMessage: true, code: 'ERR_ASSERTION', actual: Error: ENOENT: no such file or directory, lstat '/home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/.tmp.0/copy_%29/458596.sock' at cpSyncFn (node:internal/fs/cp/cp-sync:56:13) at cpSync (node:fs:3130:3) at assert.throws.code (file:///home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/parallel/test-fs-cp.mjs:381:11) at getActual (node:assert:836:5) at Function.throws (node:assert:982:24) at file:///home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/parallel/test-fs-cp.mjs:380:10 at ModuleJob.run (node:internal/modules/esm/module_job:272:25) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:580:26) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:98:5) { errno: -2, code: 'ENOENT', syscall: 'lstat', path: '/home/jayman/Documents/Home/VC/space_afraid/Git/partially_mine/node/space_afraid/test/.tmp.0/copy_%29/458596.sock' }, expected: { code: 'ERR_FS_CP_SOCKET' }, operator: 'throws' } Node.js v24.0.0-pre
…and finishes with an exit status of 1.
1
When I try following the steps to reproduce on an ext4 filesystem, the test finishes with an exit status of 0.
0
The text was updated successfully, but these errors were encountered:
pkgsi686Linux.nodejs
x86_64-linux
No branches or pull requests
Steps to reproduce
If you don’t already have one, then make a local clone of the
nodejs/node
repo by running this command:Change directory into your clone of the
node
repo by running this command:(Recommended) Switch to a Git commit where this problem is know to occur by running this command:
Build Node.js from source by following these instructions.
Run Node.js’s
test-fs-cp
test by running this command:Results
When I try following the steps to reproduce on a bcachefs filesystem, the last command prints this…
…and finishes with an exit status of
1
.When I try following the steps to reproduce on an ext4 filesystem, the test finishes with an exit status of
0
.The text was updated successfully, but these errors were encountered: