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
test.test_spwd.TestSpwdNonRoot failure with FileNotFoundError: #73341
Comments
I am building and testing Python 3.6 on the JASMIN Analysis Platform http://www.jasmin.ac.uk/services/jasmin-analysis-platform/, which runs Red Hat Enterprise Linux Server release 6.8 on a machine with 48 × Intel(R) Xeon(R) CPU E7-4860 v2 @ 2.60GHz, 2 TiB RAM, and a PanFSⓇ http://www.panasas.com/products/panfs distributed file system. test.test_spwd.TestSpwdNonRoot is failing with FileNotFoundError. Below is the full verbose output of == CPython 3.6.0 (default, Jan 4 2017, 14:11:04) [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] ====================================================================== Traceback (most recent call last):
File "/home/users/gholl/src/Python-3.6.0/Lib/test/test_spwd.py", line 67, in test_getspnam_exception
spwd.getspnam(name)
FileNotFoundError: [Errno 2] No such file or directory Ran 3 tests in 0.002s FAILED (errors=1, skipped=2) 1 test failed: Total duration: 66 ms |
Since you are seeing errors on your platform that we are not seeing, and we do not have access to your platform, you are going to have to track down the cause, I'm afraid. |
It is easy to add FileNotFoundError to the list of expected exceptions. But it seems to me that the only error that gespname() can return on Linux is EACCES. [1] May be this is a bug of your platform. |
We are seeing this too, on RHEL 7. It happens when /etc/nsswitch.conf has ...
The ldap nss back end seems to set errno = ENOENT when it gets no response from the ldap server. If we remove ldap (leaving only files), then we see errno = EACCES. Is it correct to insist on EACCES? The man page cited in the last message says only that ...
getspnam isn't one of the "functions which have int as the return value," so it isn't clear whether application code should make any assumptions about errno when it returns. |
3.6 is no longer maintained. Please create a new issue if you are seeing this problem on a current version (>= 3.9). |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: