7a56c59c

By: Tom Sydney Kerckhove <syd@cs-syd.eu>

warp/test: close the listening socket instead of faking its errno

@Vlix pointed out the better reason to do this than the one I had. A
synthesised errnoToIOError carries an errno on every platform, Windows
included, so a test built on one would keep passing there while a real
close behaves differently. Closing the socket exercises whatever the
platform actually produces.

My reason for faking it was that closing a descriptor the accept loop is
parked on does not go well. That does not apply here: the close happens
inside the accept action, so the loop is between accepts rather than
inside one, and the accept that follows fails on a descriptor that is
already -1.

Timeline