-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
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
investigate failing test-fs-readdir-ucs2 on Raspberry Pi #14028
Labels
build
Issues and PRs related to build files or the CI.
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
fs
Issues and PRs related to the fs subsystem / file system.
test
Issues and PRs related to the tests.
Comments
Trott
added
build
Issues and PRs related to build files or the CI.
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
fs
Issues and PRs related to the fs subsystem / file system.
test
Issues and PRs related to the tests.
labels
Jul 1, 2017
2 tasks
Fix in #14029 |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 3, 2017
If the filesystem does not support UCS2, do not run the test. Fixes: nodejs#14028
Two follow up issues:
$ NVM_NODEJS_ORG_MIRROR=https://nodejs.org/download/nightly Now using node v9.0.0-nightly20170703fe730d34ce (npm v5.0.3)
$ node test/parallel/test-fs-readdir-ucs2.js
/mnt/d/code/node-cur/test/parallel/test-fs-readdir-ucs2.js:22
throw e;
^
Error: ENOENT: no such file or directory, open '/mnt/d/code/node-cur/test/tmp/=�♦�'
at Object.fs.openSync (fs.js:651:18)
at Object.<anonymous> (/mnt/d/code/node-cur/test/parallel/test-fs-readdir-ucs2.js:18:19)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
at Function.Module.runMain (module.js:605:10)
at startup (bootstrap_node.js:158:16)
at bootstrap_node.js:575:3 and assertion fails on native WSL volume: refael@refaelux:~/node$ node test/parallel/test-fs-readdir-ucs2.js
assert.js:55
throw new errors.AssertionError({
^
AssertionError [ERR_ASSERTION]: <Buffer 3d d8 04 dc> deepStrictEqual <Buffer 3d ef bf bd 04 ef bf bd>
at fs.readdir.common.mustCall (/home/refael/node/test/parallel/test-fs-readdir-ucs2.js:29:10)
at /home/refael/node/test/common/index.js:518:15
at FSReqWrap.oncomplete (fs.js:135:15) |
Trott
added a commit
to Trott/io.js
that referenced
this issue
Aug 15, 2017
If the filesystem does not support UCS2, do not run the test. PR-URL: nodejs#14029 Fixes: nodejs#14028 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
MylesBorins
pushed a commit
that referenced
this issue
Aug 16, 2017
If the filesystem does not support UCS2, do not run the test. Backport-PR-URL: #14835 PR-URL: #14029 Fixes: #14028 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
MylesBorins
pushed a commit
that referenced
this issue
Sep 5, 2017
If the filesystem does not support UCS2, do not run the test. Backport-PR-URL: #14835 PR-URL: #14029 Fixes: #14028 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Ping @nodejs/testing we should probably investigate this again and run a stress test. It would be great to get a green CI before the next Code & Learn. |
As far as I can tell this has been resolved? Feel free to re-open if I'm reading that incorrectly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
build
Issues and PRs related to build files or the CI.
flaky-test
Issues and PRs related to the tests with unstable failures on the CI.
fs
Issues and PRs related to the fs subsystem / file system.
test
Issues and PRs related to the tests.
From nodejs/build#774:
The text was updated successfully, but these errors were encountered: