This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: test_socket failures on Debian unstable
Type: behavior Stage:
Components: Tests Versions: Python 3.2
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: doko, lekma, nvetoshkin, pitrou
Priority: normal Keywords: buildbot

Created on 2010-10-14 16:09 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (6)
msg118677 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-10-14 16:09
This is following r85480 (issue #7523). It seems the Debian unstable system on one of the buildbots has SOCK_NONBLOCK and SOCK_CLOEXEC, but doesn't support creating sockets using these flags:

======================================================================
ERROR: testInitNonBlocking (test.test_socket.NonBlockingTCPTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/test/test_socket.py", line 914, in testInitNonBlocking
    socket.SOCK_NONBLOCK)
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/socket.py", line 94, in __init__
    _socket.socket.__init__(self, family, type, proto, fileno)
socket.error: [Errno 22] Invalid argument

======================================================================
ERROR: test_SOCK_CLOEXEC (test.test_socket.CloexecConstantTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/test/test_socket.py", line 1834, in test_SOCK_CLOEXEC
    socket.SOCK_STREAM | socket.SOCK_CLOEXEC)
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/socket.py", line 94, in __init__
    _socket.socket.__init__(self, family, type, proto, fileno)
socket.error: [Errno 22] Invalid argument

======================================================================
ERROR: test_SOCK_NONBLOCK (test.test_socket.NonblockConstantTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/test/test_socket.py", line 1854, in test_SOCK_NONBLOCK
    socket.SOCK_STREAM | socket.SOCK_NONBLOCK)
  File "/home/doko/buildarea/3.x.klose-debian-alpha/build/Lib/socket.py", line 94, in __init__
    _socket.socket.__init__(self, family, type, proto, fileno)
socket.error: [Errno 22] Invalid argument

(full log at http://www.python.org/dev/buildbot/3.x/builders/alpha%20Debian%203.x/builds/258/steps/test/logs/stdio)
msg118680 - (view) Author: Vetoshkin Nikita (nvetoshkin) Date: 2010-10-14 16:20
What about kernel version? As far as I know 2.6.27 is minimum requirement.
msg118684 - (view) Author: Vetoshkin Nikita (nvetoshkin) Date: 2010-10-14 16:26
Here's the patch from debian's issue http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529920
Patch URL: https://patches.ubuntu.com/by-release/extracted/ubuntu/n/neon27/0.28.4-2/01_runtime_detect_sock_cloexec.dpatch
msg118686 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-10-14 16:35
Thanks for the research. Given that it only happens on Debian unstable, and it only happens if you explicitly use SOCK_{CLOEXEC,NONBLOCK}, I would vote for not adding a workaround until some supported OS also exhibits the issue.
msg118687 - (view) Author: Vetoshkin Nikita (nvetoshkin) Date: 2010-10-14 16:39
Agree.
Already written code won't suffer, new code should be ready to use new linux kernel.
msg125267 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2011-01-04 00:55
Fixed some time ago.
History
Date User Action Args
2022-04-11 14:57:07adminsetgithub: 54313
2011-01-04 00:55:22pitrousetstatus: open -> closed

messages: + msg125267
resolution: out of date
nosy: doko, pitrou, lekma, nvetoshkin
2010-10-14 16:39:21nvetoshkinsetmessages: + msg118687
2010-10-14 16:35:49pitrousetmessages: + msg118686
2010-10-14 16:26:08nvetoshkinsetmessages: + msg118684
2010-10-14 16:20:24nvetoshkinsetmessages: + msg118680
2010-10-14 16:09:32pitroucreate