Skip to content

fix(ci): retry relay container start on port conflict#111041

Merged
mchen-sentry merged 2 commits intomasterfrom
fix/mingchen/relay_docker_race
Mar 19, 2026
Merged

fix(ci): retry relay container start on port conflict#111041
mchen-sentry merged 2 commits intomasterfrom
fix/mingchen/relay_docker_race

Conversation

@mchen-sentry
Copy link
Member

Retry containers.run() in the relay_server fixture when Docker returns "address already in use", giving the kernel time to release the host port binding from the previous container removal.

More load for Docker daemon under xdist is probably why this happened.

@mchen-sentry mchen-sentry marked this pull request as ready for review March 18, 2026 22:19
@mchen-sentry mchen-sentry requested a review from a team as a code owner March 18, 2026 22:19
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 18, 2026
@mchen-sentry mchen-sentry requested a review from joshuarli March 18, 2026 22:19
Retry containers.run() in the relay_server fixture when Docker returns
"address already in use", giving the kernel time to release the host
port binding from the previous container removal. Uses exponential
backoff (5 attempts) for more wiggle room under load.
@mchen-sentry mchen-sentry merged commit 8bd0bd8 into master Mar 19, 2026
78 of 79 checks passed
@mchen-sentry mchen-sentry deleted the fix/mingchen/relay_docker_race branch March 19, 2026 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants