[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

Ronald Oussoren added the comment: The reproducer script and .c file I added earlier do not fail with "Cannot allocate memory" on macOS 12.0.1. I haven't checked yet if this is enough to avoid test failures in the (now skipped) testFDPassEmpty. --

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

Ronald Oussoren added the comment: The issue is still present with python 3.9 and macOS 10.15 as well as current macOS 11 betas. The following python scriptlet reproduces the issue: # --- import socket sd1, sd2 = socket.socketpair() sd1.sendmsg([b"hello"], [(socket.SOL_SOCKET,

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

Change by Brett Cannon : -- nosy: -brett.cannon ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

STINNER Victor added the comment: Ned Deily: > This issue slipped off the radar (so to speak) after being closed. For one, > the tests also fail on 3.5.x (and probably earlier systems) and fail on macOS > 10.12, not just 10.11. And, two, I'm not sure if anyone opened an issue with > Apple

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

STINNER Victor added the comment: New changeset 5e9c1101924bacf3ead03124b5c1e48551638360 by Victor Stinner in branch '3.5': bpo-24725: Skip the test_socket.testFDPassEmpty on OS X (#1427) https://github.com/python/cpython/commit/5e9c1101924bacf3ead03124b5c1e48551638360 -- nosy:

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

Changes by STINNER Victor : -- pull_requests: +1532 ___ Python tracker ___ ___

[issue24725] test_socket testFDPassEmpty fails on OS X 10.11+ with "Cannot allocate memory"

Ned Deily added the comment: This issue slipped off the radar (so to speak) after being closed. For one, the tests also fail on 3.5.x (and probably earlier systems) and fail on macOS 10.12, not just 10.11. And, two, I'm not sure if anyone opened an issue with Apple about it. I'm re-opening