Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fixed failing tests due to the change we check for file readability. #9
base: master
Are you sure you want to change the base?
Fixed failing tests due to the change we check for file readability. #9
Changes from 3 commits
fa05913
7299137
5ff7fe4
473782c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I strongly suggest not to use
t.Fatal*
, unless you really want to abort the test. Better to uset.Error*
.t.Error*
-> t.Log + t.Fail, which marks the testcase as failed, but continuest.Fatal*
-> t.Log + t.FailNow, which aborts the current test functionSame applies to the following test cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if
syscall.ENOENT
isn't a way to specific here, the more generalos.ErrNotExist
should be better suitable, IMHO. I'm not sure about portability of ENOENT (maybe other systems report an other errno, which hopefully will be translated by the Go libraries intoos.ErrNotExist
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The system returns "no such file or directory". I found that this string comes from
syscall.ENOENT
and just used it as a sentinel error.os.ErrNotExist
contains "file does not exist", which is a different string.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The syscall package is os dependend.
e.g. shows different things. Fortunately for the current situation,
syscall.ENOENT
seems to be available in both cases. But do we know about other OS?I'd suggest, using the highest abstraction available, which is
os.ErrNotExist
, IMHO