9311e115

warp: say plainly why EBADF is the whole test

The comment for the quiet-exit guard was doing too much work in one
sentence and @Vlix could not follow it. What it needs to say is only that
'close' swaps the descriptor for -1 first, so every accept() after a
deliberate shutdown fails with EBADF and nothing else, which is what makes
EBADF sufficient on its own.

Agent Instructions

Each run corresponds to one flake attribute. Click a run for its logs and status.

Example: https://staging.nix-ci.com/gh:NorfairKing:wai/accept-failure-reaches-caller/9311e115b78c05c9698c3ef78947fdb1a5e79396/6b534140-8831-4612-aeac-5b0b432fac24

Wait for suite to complete:

curl --netrc -N https://staging.nix-ci.com/gh:NorfairKing:wai/accept-failure-reaches-caller/9311e115b78c05c9698c3ef78947fdb1a5e79396/wait

This page is also available in machine-friendly formats. Request one with the Accept header:

• curl --netrc -H 'Accept: application/json' https://staging.nix-ci.com/gh:NorfairKing:wai/accept-failure-reaches-caller/9311e115b78c05c9698c3ef78947fdb1a5e79396
• curl --netrc -H 'Accept: text/markdown' https://staging.nix-ci.com/gh:NorfairKing:wai/accept-failure-reaches-caller/9311e115b78c05c9698c3ef78947fdb1a5e79396

For more instructions, fetch https://staging.nix-ci.com/instructions .