fix(ci): retry relay container start on port conflict#111041
Merged
mchen-sentry merged 2 commits intomasterfrom Mar 19, 2026
Merged
fix(ci): retry relay container start on port conflict#111041mchen-sentry merged 2 commits intomasterfrom
mchen-sentry merged 2 commits intomasterfrom
Conversation
joshuarli
reviewed
Mar 18, 2026
joshuarli
approved these changes
Mar 18, 2026
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.
1f60f5b to
0c30abe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Retry
containers.run()in therelay_serverfixture 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.