-
-
Notifications
You must be signed in to change notification settings - Fork 115
3.12.0: test_bad_lock_file[current_directory-UnixFileLock] fails #233
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
Comments
I see the current fix is to omit this test which will work, since this is an edgecase of the test, not of filelock. I'd like a little more information though so we can see about a permanent fix. Sorry I am not familiar with OpenIndiana / SunOS. What is For this OS, I assume the expected error for trying to open "." as if it were a file is
|
|
This is interesting. Based on the Oracle page, I would have thought the error message would be EISDIR. If you can explain this, I'd love to know. |
Can you try another thing for me? Want to make sure I understand how this is behaving.
|
Considering the reason for this test case was because of a Windows specific error (#231), I think it may be reasonable to change the check so "if non-windows, make sure the result isn't EPERM". |
This should be done now, the CI passes at least with 3.12. |
During upgrade of the filelock package for OpenIndiana from version 3.11.0 to version 3.12.0 I noticed that one test fails (with version 3.11.0 all tests passed):
The text was updated successfully, but these errors were encountered: