Author aeros
Recipients abacabadabacaba, achimnol, aeros, asvetlov, fantix, lukasz.langa, miss-islington, ned.deily, vstinner, yselivanov
Date 2020-06-14.06:20:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592115647.17.0.980000261603.issue30064@roundup.psfhosted.org>
In-reply-to
Content
No problem at all, and thanks for clarifying.

> If enlarging the timeout works in some of your cases, that really inspires me on a potential cause of the issue in the test. To simulate the race condition specifically for loop.sock_sendall(), I needed a connected socket with a full send buffer so that the next sock_sendall() call would block. To achieve this, I wrote something like this:

> It might be that it cost too much time in these loops (especially the 2nd one because the logs showed that it was blocked on calling sock_sendall()). But that's just a guess yet, let me add some more debug logs and test locally.

That seems reasonable to me and would make the most sense at a glance. If this is confirmed to be the source of the issue, we should be able to just reduce the size of the socket's send buffer via SO_SNDBUF before sending to it so that it fills up much more quickly.
History
Date User Action Args
2020-06-14 06:20:47aerossetrecipients: + aeros, vstinner, fantix, ned.deily, asvetlov, abacabadabacaba, lukasz.langa, yselivanov, achimnol, miss-islington
2020-06-14 06:20:47aerossetmessageid: <1592115647.17.0.980000261603.issue30064@roundup.psfhosted.org>
2020-06-14 06:20:47aeroslinkissue30064 messages
2020-06-14 06:20:47aeroscreate