-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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 error on AIX #55401
Comments
I have the following error in test_socket on AIX: ====================================================================== Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 640, in testGetaddrinfo
self.assertEqual(socktype, socket.SOCK_STREAM)
AssertionError: 0 != 1 Ran 158 tests in 16.904s FAILED (failures=1, skipped=4)
Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 2012, in <module>
test_main()
File "./Lib/test/test_socket.py", line 2008, in test_main
support.run_unittest(*tests)
File "/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py", line 1145, in run_unittest
_run_suite(suite)
File "/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/support.py", line 1128, in _run_suite
raise TestFailed(err)
test.support.TestFailed: Traceback (most recent call last):
File "./Lib/test/test_socket.py", line 640, in testGetaddrinfo
self.assertEqual(socktype, socket.SOCK_STREAM)
AssertionError: 0 != 1 [119732 refs] I haven't investigated yet. |
I am not sure this is directly related, but test_socket.py will hang forever on AIX 6.1 when this script is run as part of "make buildbottest". It won't hang when running the script alone. |
not a python problem, see closed aix issue http://www-01.ibm.com/support/docview.wss?uid=isg1IZ57712 |
Same error with Python 2.7.3 on AIX 6.1 |
FYI: test fails on AIX 5.3 TL7 SP0 (as expected. The IBM document refers to 5.3 TL8) On AIX 6.1 TL9 SP5 (and probably earlier) the test passes. IMHO - can be closed (and README.AIX can be updated). michael@x071:[/data/prj/aixtools/python/python-2.7.11.5/Lib/test]oslevel -q -s | head -5 michael@x071:[/data/prj/aixtools/python/python-2.7.11.5/Lib/test]../../python test_socket.py OK (skipped=7) On AIX 5.3 (the expected fail...) root@x064:[/data/prj/aixtools/python/python-2.7.11.5/Lib/test]../../python test_socket.py ... ====================================================================== Traceback (most recent call last):
File "test_socket.py", line 691, in testGetaddrinfo
self.assertEqual(socktype, socket.SOCK_STREAM)
AssertionError: 0 != 1 Ran 124 tests in 16.765s FAILED (failures=1, skipped=7)
Traceback (most recent call last):
File "test_socket.py", line 1804, in <module>
test_main()
File "test_socket.py", line 1800, in test_main
test_support.run_unittest(*tests)
File "/data/prj/aixtools/python/python-2.7.11.5/Lib/test/test_support.py", line 1428, in run_unittest
_run_suite(suite)
File "/data/prj/aixtools/python/python-2.7.11.5/Lib/test/test_support.py", line 1411, in _run_suite
raise TestFailed(err)
test.test_support.TestFailed: Traceback (most recent call last):
File "test_socket.py", line 691, in testGetaddrinfo
self.assertEqual(socktype, socket.SOCK_STREAM)
AssertionError: 0 != 1 |
Back to master (python3-3.7) (note: not your problem - but this link is gone: not a python problem, see closed aix issue http://www-01.ibm.com/support/docview.wss?uid=isg1IZ57712) Getting this (obviously) on AIX 5.3, but also on AIX 6.1 (TL6), but not on AIX 7.1 TL2: (both gcc and xlc) testGetSockOpt (test.test_socket.GeneralModuleTests) ... ok However, what I get on all three systems (but do not see on the AIX buildbot running on AIX 7.2, and I have no access to AIX 7.2) is: AIX 6.1: FAILED (failures=1, errors=114, skipped=119) AIX 7.1: Ran 669 tests in 25.917s FAILED (errors=114, skipped=119) What all the ERRORS have in common is: File "/data/prj/python/git/x067-python3-3.7/Lib/test/test_socket.py", line 2373, in setUp HTH - (and still digging) |
I have tried jumping into the pdp using but do not come much further in understanding how the expectations expressed in these comments are satisfied: +2153 # Tests for the sendmsg()/recvmsg() interface. Where possible, the ++ Details ++ ()
|
The original error reported was fixed by AIX - in AIX 6.1. It will remain unresolved in AIX 5.3. There are currently two other errors in test_socket. FAIL: test_getnameinfo_ipv6_scopeid_symbolic (test.test_socket.GeneralModuleTests) Traceback (most recent call last):
File "/data/prj/python/git/python3-3.7/Lib/test/test_socket.py", line 1649, in test_getnameinfo_ipv6_scopeid_symbolic
self.assertEqual(nameinfo, ('ff02::1de:c0:face:8d%' + test_interface, '1234'))
AssertionError: Tuples differ: ('ff02::1de:c0:face:8d', '1234') != ('ff02::1de:c0:face:8d%en0', '1234') First differing element 0:
I assume the capital D in the argument in the test: is meant to trigger getting the IPv6 zoneinfo based on ifindex. AIX does have a routine to strip zoneinfo off an IPv6 address, but the getnameinfo() and getaddrinfo() do not support this. I can create a new issue specifically for IPv6 zone id issue, or I can add a PR here. Please advise (the PR is merely adding "skipUnless" logic to test_socket.py. ERROR: test_getaddrinfo_ipv6_scopeid_symbolic |
I nearly have a patch - to resolve all the remaining test_socket() issues with AIX. However, this (new?) issue remains: f = lambda a: inet_pton(AF_INET6, a)
assertInvalid = lambda a: self.assertRaises(
(OSError, ValueError), f, a
) >>> f('1:2:3:4:5:6:7:8')
b'\x00\x01\x00\x02\x00\x03\x00\x04\x00\x05\x00\x06\x00\x07\x00\x08'
>>> f('1:2:3:4:5:6:7:8:')
b'\x00\x01\x00\x02\x00\x03\x00\x04\x00\x05\x00\x06\x00\x07\x00\x08'
>>> f('1::')
b'\x00\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
>>> f('1:2:3:4:5:6:7:8::')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 1, in <lambda>
OSError: illegal IP address string passed to inet_pton
>>> f('1:2:3:4:5:6:7')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 1, in <lambda>
OSError: illegal IP address string passed to inet_pton Is, maybe, the last test meant to be '::' on the end, rather than ':'? |
Could this also be backported to Version 3.7 and 3.6 (I do not expect it to be backported to 2.7, but I had mistakenly removed it 2.7 when I changed it to 3.8 - and should have added 3.6 and 3.7 then). |
On 10/03/2019 19:40, Michael Felt wrote:
|
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: