[issue10104] test_socket failures on Debian unstable

Antoine Pitrou added the comment: Fixed some time ago. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ _

[issue10104] test_socket failures on Debian unstable

Vetoshkin Nikita added the comment: Agree. Already written code won't suffer, new code should be ready to use new linux kernel. -- ___ Python tracker ___ __

[issue10104] test_socket failures on Debian unstable

Antoine Pitrou added the comment: 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. -- __

[issue10104] test_socket failures on Debian unstable

Vetoshkin Nikita added the comment: 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 -- __

[issue10104] test_socket failures on Debian unstable

Vetoshkin Nikita added the comment: What about kernel version? As far as I know 2.6.27 is minimum requirement. -- ___ Python tracker ___

[issue10104] test_socket failures on Debian unstable

New submission from Antoine Pitrou : 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: =