• chore: retry postgres connection on reset by peer in tests #18632 👈(View in Graphite)
• main

This stack of pull requests is managed byGraphite. Learn more aboutstacking.

I believe a much simpler fix is this:#18423.openContainer uses a flock to serialize multiple binaries trying to start a postgres container at the same time, and has an early exit path if the container was already started. Do you see a reason this wouldn't be sufficient?

That assumes that "reset by peer" can only happen if there is already a Docker container with the name we expect starting on the port.

If it uses a different name, or a non-Dockerized postgres is responsible for "reset by peer" then starting the container will fail due to port conflict, no?