Test failure: "not ok 94 - client, refused on write"
I've just observed this test failure:
# refused connections
ok 86 - server, create server
ok 87 - check getsockname return
ok 88 - server, start listening
ok 89 - client, connect
ok 90 - client, successful write
ok 91 - client, timeout on read
ok 92 - client, connect
ok 93 - server, close socket
# wanted: -980
# seen: 1
not ok 94 - client, refused on write
After quickly reading the relevant test code and this Stack Overflow answer, it seems that the test could be buggy:
https://stackoverflow.com/questions/11436013/writing-to-a-closed-local-tcp-socket-not-failing
Even though in the Stack Overflow question the client and server roles are reversed with respect to the test scenario, it still seems that writing to the client socket while the server socket has been closed may not necessarily fail (at least, immediately)?