Skip to content

ENOENT or ENOTDIR in fs module #3850

Closed
Closed
@rifler

Description

@rifler

There is a test here for fs.openSync open non-existent file. It should raise ENOENT error.

But on my mac os 10.10.5 with node 5.0.0 installed via homebrew this test raised ENOTDIR error.

Is it expected behaviour?

Metadata

Metadata

Assignees

No one assigned

    Labels

    fsIssues and PRs related to the fs subsystem / file system.macosIssues and PRs related to the macOS platform / OSX.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions