Aleksei Sviridkin 3cf9431f1e test(redis): fail the negative dial probes on an unread state ...

The two negative dials in the chainsaw suite, the plaintext dial at a
TLS instance and the TLS dial at the instance whose flip was rejected,
decided by whether PONG appeared on stdout with stderr discarded. A
missing pod, a 403 on exec, a wrong container name or the outer cap
firing print no PONG either, so each of them passed as the refusal
being asserted, and the flip case is the check that a rejected flip
left TLS off.

Keep what the dial printed and pass only on the refusal each listener
actually gives, verified in the shipped images: a TLS listener drops a
plaintext client at AUTH and redis-cli reports it as an I/O error; a
plaintext listener holds a ClientHello in silence, because the inline
parser's newline scan stops at a NUL in the handshake header, so the
inner cap expires and kubectl's exit-code trailer carries the 124.
That trailer is what separates the cap firing inside the pod from the
wrapper's cap firing outside it. A listener that answers PONG fails
the check, and anything else fails as a state the check did not read,
with the dial's output in the message.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-09-02 20:48:52 +03:00

..

chainsaw-test.yaml

test(redis): fail the negative dial probes on an unread state

2026-09-02 20:48:52 +03:00

redis-flip-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis-flip.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis-tls.yaml

test(redis): exercise TLS end to end in the chainsaw suite

2026-09-02 17:58:06 +03:00

redis.yaml

test(e2e): migrate app suite from BATS to Chainsaw and wire into CI

2026-06-25 13:42:34 +05:00