summaryrefslogtreecommitdiffstats
path: root/Lib/configparser.py
diff options
context:
space:
mode:
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>2018-09-28 13:07:56 (GMT)
committerVictor Stinner <vstinner@redhat.com>2018-09-28 13:07:56 (GMT)
commit007fda436f707ac95c2fa8f8886efd9e09d5b630 (patch)
treefd0c4fc6303d2381041b2d3170817752c4fe5cbf /Lib/configparser.py
parent7e35081bc828291da5793db49ab45dee4fda5043 (diff)
downloadcpython-007fda436f707ac95c2fa8f8886efd9e09d5b630.zip
cpython-007fda436f707ac95c2fa8f8886efd9e09d5b630.tar.gz
cpython-007fda436f707ac95c2fa8f8886efd9e09d5b630.tar.bz2
bpo-34521: Fix tests in test_multiprocessing_spawn to use correctly CMSG_SPACE (GH-9613) (GH-9619)
After some failures in AMD64 FreeBSD CURRENT Debug 3.x buildbots regarding tests in test_multiprocessing_spawn and after examining similar failures in test_socket, some errors in the calculation of ancillary data buffers were found in multiprocessing.reduction. CMSG_LEN() can often be used as the buffer size for recvmsg() to receive a single item of ancillary data, but RFC 3542 requires portable applications to use CMSG_SPACE() and thus include space for padding, even when the item will be the last in the buffer. The failures we experience are due to the usage of CMSG_LEN() instead of CMSG_SPACE(). (cherry picked from commit 077061a7b24917aaf31057885c69919c5a553c88) Co-authored-by: Pablo Galindo <Pablogsal@gmail.com>
Diffstat (limited to 'Lib/configparser.py')
0 files changed, 0 insertions, 0 deletions