By: Tom Sydney Kerckhove <syd@cs-syd.eu>
warp/test: stop the accept loop the way a closed socket does The test ended the accept loop with a userError, which warp reads as an accept() that broke on its own. A real closed listening socket gives EBADF, arriving as InvalidArgument, and that is the case the test means to stand for. It also matters for anything that changes how accept failures are handled. With #1106, which rethrows accept errors other than the deliberate close, a userError propagates out of runSettingsSocket and this test fails, making the two branches unmergeable together for no reason beyond the test having picked the wrong error.
| Time to Start | Worker time | Duration | Time to finish | Idle | |
| Config | 0s | 2s | 2s | 2s | 0s |
| Eval | - | - | - | - | - |
| Build | - | - | - | - | - |
| Suite | 0s | 2s | 2s | 2s | 0s |