test: use different port number for tests to account for port being in TIME_WAIT state after a process terminates#524
Merged
Conversation
e9c45ef to
194890a
Compare
194890a to
cfcc536
Compare
cfcc536 to
a11c9e6
Compare
8896ff7 to
84a25be
Compare
84e3229 to
f95dbc6
Compare
d68ea51 to
9ad4d23
Compare
cab69ff to
7673916
Compare
kaiokmo
previously approved these changes
Mar 11, 2026
7673916 to
b4df961
Compare
The webhook server takes longer than 15 seconds to come up depending on the load in the servers running the CI. Increasing the timeout to 60 seconds to see if it performs better, also log the Exception that is caught Use distinct port numbers so that we dont run into TIME_WAIT issues when the TCP stack is still holding on to the port.
dcf52c3 to
5031afc
Compare
for more information, see https://pre-commit.ci
ttuffin
approved these changes
Mar 12, 2026
kaiokmo
approved these changes
Mar 12, 2026
AlexSCorey
pushed a commit
to AlexSCorey/event-driven-ansible
that referenced
this pull request
Mar 17, 2026
…n TIME_WAIT state after a process terminates (ansible#524) * test: bump timeout to 60 seconds The webhook server takes longer than 15 seconds to come up depending on the load in the servers running the CI. Increasing the timeout to 60 seconds to see if it performs better, also log the Exception that is caught Use distinct port numbers so that we dont run into TIME_WAIT issues when the TCP stack is still holding on to the port. * chore: auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
AlexSCorey
pushed a commit
to AlexSCorey/event-driven-ansible
that referenced
this pull request
Mar 17, 2026
…n TIME_WAIT state after a process terminates (ansible#524) * test: bump timeout to 60 seconds The webhook server takes longer than 15 seconds to come up depending on the load in the servers running the CI. Increasing the timeout to 60 seconds to see if it performs better, also log the Exception that is caught Use distinct port numbers so that we dont run into TIME_WAIT issues when the TCP stack is still holding on to the port. * chore: auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
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.
When tests run sequentially in CI, the operating system doesn't release port 5000 immediately
after a process terminates. There's a brief period (usually a few seconds) where the port remains
in TIME_WAIT state.
Changed to use separate ports for the tests.
https://github.com/ansible/event-driven-ansible/actions/runs/22968325889/job/66678006614