Three tests stand a bare `new \Redis()` in for a store that cannot be
read. That holds on phpredis 5, where every command of such an object
throws. Since phpredis 6 the object dials 127.0.0.1:6379 on its first
command, so the tests passed only while nothing answered there. The
PHPUnit job installs a Redis on that port, and ConnectionTouchTest
failed once on a pull request that does not touch the cluster code
(#363).
RedisServer::unreachable() returns a client whose connect() to a
missing socket failed: it dials nothing on either version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AneTzAHPPkYWPQjwyZ2td9
Seven unit tests started redis-server on a random port in 20000-40000 (it
overlaps the kernel's ephemeral range, so it can be taken) and gave it
2.5 s to listen, then went on whether or not it did. On a busy runner
ConnectionIngestIdempotencyTest's redis cases failed with "Connection
refused" (PR #319's CI). ConnectionDivergenceTest already had the fix;
it now lives in tests/Support/RedisServer: a port the kernel picks free,
up to 10 s to listen, and a server that never listens is redis not
available, so its tests skip instead of erroring.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CWvQvZGYnikZ2bx17R6fN6
