0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-30 15:30:56 +01:00
nodejs/test/known_issues
Rich Trott b6e301a9e0 test: add test-fs-writeFileSync-invalid-windows
Add a known_issues test for the Windows returning ENOTFOUND where EINVAL
is more appropriate. This happens with various functions in the `fs`
module when an invalid path is used.

Refs: https://github.com/nodejs/node/issues/8987

PR-URL: https://github.com/nodejs/node/pull/28569
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
2019-07-11 10:27:42 -07:00
..
known_issues.status test: fix flaky test-vm-timeout-escape-nexttick 2019-07-02 06:49:40 +02:00
test-cwd-enoent-file.js
test-dgram-bind-shared-ports-after-port-0.js
test-fs-writeFileSync-invalid-windows.js test: add test-fs-writeFileSync-invalid-windows 2019-07-11 10:27:42 -07:00
test-http-path-contains-unicode.js
test-inspector-cluster-port-clash.js
test-repl-require-context.js
test-stdin-is-always-net.socket.js
test-url-parse-conformance.js
test-vm-ownkeys.js
test-vm-ownpropertynames.js
test-vm-ownpropertysymbols.js
test-vm-timeout-escape-nexttick.js test: fix flaky test-vm-timeout-escape-nexttick 2019-07-02 06:49:40 +02:00
test-vm-timeout-escape-promise.js
test-vm-timeout-escape-queuemicrotask.js
testcfg.py