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_socket.py fails #45951
Comments
Checkout Python 2.5 from release25-maint branch, revision 59479, [~/python-2.5]> LD_LIBRARY_PATH=/home/cartman/python-2.5: ./python ====================================================================== Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 344, in testGetServBy
eq(socket.getservbyport(port2), service)
error: port/proto not found Ran 68 tests in 5.558s FAILED (errors=1)
Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 995, in <module>
test_main()
File "./Lib/test/test_socket.py", line 991, in test_main
test_support.run_unittest(*tests)
File "/home/cartman/python-2.5/Lib/test/test_support.py", line 441, in
run_unittest
run_suite(suite, testclass)
File "/home/cartman/python-2.5/Lib/test/test_support.py", line 426, in
run_suite
raise TestFailed(err)
test.test_support.TestFailed: Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 344, in testGetServBy
eq(socket.getservbyport(port2), service)
error: port/proto not found |
What happens if you do NOT change the library path in front of it? |
Then it won't run as expected (I got python 2.4 installed system wise) : ./python: error while loading shared libraries: libpython2.5.so.1.0: |
Any other thing I can do to debug this? |
Yes, can you tell us the content of port2 and service? |
This was a glibc regression on my side, it can be closed as invalid. Thanks! |
Reproducable with Python3.0rc1 on Debian lenny, only when nscd is running. Not a Python bug. |
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: