Skip to content

test: add test-fs-writeFileSync-invalid-windows - #28569

Merged
Trott merged 1 commit into
nodejs:masterfrom
Trott:known-8987
Jul 11, 2019
Merged

test: add test-fs-writeFileSync-invalid-windows#28569
Trott merged 1 commit into
nodejs:masterfrom
Trott:known-8987

Conversation

@Trott

@TrottTrott commented Jul 5, 2019

Copy link
Copy Markdown
Member

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: #8987

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Jul 5, 2019
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@lpinca

Copy link
Copy Markdown
Member

Why it fails when skipped?

@Trott

Copy link
Copy Markdown
MemberAuthor

Why it fails when skipped?

Because known_issues tests are expected to fail. At least one other test uses assert.fail() instead of common.skip() and includes a comment that says to change it to common.skip() when the issue is resolved and the test is moved out of known_issues. So I'll probably do that with this test.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@TrottTrott added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Jul 10, 2019
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: nodejs#8987
PR-URL: nodejs#28569
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
@Trott

Copy link
Copy Markdown
MemberAuthor

Landed in b6e301a

@Trott
Trott merged commit b6e301a into nodejs:masterJul 11, 2019
@Trott
Trott deleted the known-8987 branch July 11, 2019 17:30
targos pushed a commit that referenced this pull request Jul 20, 2019
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: #8987
PR-URL: #28569
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This was referenced Jul 23, 2019
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@Trott@nodejs-github-bot@lpinca@cjihrig@BridgeAR