Message321877
| Author | vstinner |
|---|---|
| Recipients | njs, pitrou, vstinner, yselivanov |
| Date | 2018-07-18.10:38:34 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1531910314.53.0.56676864532.issue34130@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Using "write.setsockopt(socket.SOL_SOCKET, socket.SO_SNDBUF, 0)", I ran a stress test on test_socket() in 3 different terminals and I failed to reproduce the bug, whereas the same test (in 3 terminals) usually reproduces the bug in less than 30 seconds. Using "write.setsockopt(socket.SOL_SOCKET, socket.SO_SNDBUF, 1)", I still reproduce the bug. It seems like Windows behaves differently with SO_SNDBUF=0 as if the socket has really no kernel buffer and so respects user preference for SO_SNDBUF=0 ;-) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-07-18 10:38:34 | vstinner | set | recipients: + vstinner, pitrou, njs, yselivanov |
| 2018-07-18 10:38:34 | vstinner | set | messageid: <1531910314.53.0.56676864532.issue34130@psf.upfronthosting.co.za> |
| 2018-07-18 10:38:34 | vstinner | link | issue34130 messages |
| 2018-07-18 10:38:34 | vstinner | create | |