| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
It seems some tests fail with this, some tmp files weren't properly cleaned up after the test finished. Can't clean tmpdir: /home/iojs/tmp/.tmp.261
Files blocking: [ '.nfs00000000019201330000031d' ]
Note: ".nfs*" might be files that were open and unlinked but not closed.
See http://nfs.sourceforge.net/#faq_d2 for details.
/home/iojs/build/workspace/node-test-binary-arm/test/common/tmpdir.js:55
throw e;
^
Error: ENOTEMPTY: directory not empty, rmdir '/home/iojs/tmp/.tmp.261'
at Object.rmdirSync (node:fs:1157:10)
at _rmdirSync (node:internal/fs/rimraf:260:21)
at rimrafSync (node:internal/fs/rimraf:193:7)
at Object.rmSync (node:fs:1204:10)
at rmSync (/home/iojs/build/workspace/node-test-binary-arm/test/common/tmpdir.js:9:6)
at process.onexit (/home/iojs/build/workspace/node-test-binary-arm/test/common/tmpdir.js:40:5)
at process.emit (node:events:406:35) {
errno: -39,
syscall: 'rmdir',
code: 'ENOTEMPTY',
path: '/home/iojs/tmp/.tmp.261'
}
I can't see why this PR would result in a difference, is it a test util bug? @nodejs/testing |
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
|
This doesn't land cleanly on v14.x-staging. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Refs: #35711