Charles-François Natali added the comment:
It might be a different test triggering the buffer overflow, but the underlying
cause is the same as #20937.
--
nosy: +neologix
resolution: -> duplicate
stage: -> committed/rejected
status: open -> closed
superseder: -> test_socket: buffer o
New submission from Jeffrey Walton:
Test 240 also suffers from a buffer overflow on sock_recvmsg_guts.
Test 240 is the test that follows 239, and 239 is "[239/389/2] test_unittest".
(I don't believe the message for 239 has flushed).
=
