Skip to content

Conversation

PeterAdams-A
Copy link
Collaborator

Motivation:

The above test has been seen to fail with port already in use. The test assumes that a port can be bound to twice in a row. It's possible that another process takes the port between the two binds - this can be stopped by binding a second time before stopping the first.

Modifications:

Allow port reuse and reorder the test to bind a second time before releasing the first.

Result:

Test should no longer be flaky.

Motivation:

The above test has been seen to fail with port already in use.
The test assumes that a port can be bound to twice in a row.
It's possible that another process takes the port between the two
binds - this can be stopped by binding a second time before stopping
the first.

Modifications:

Allow port reuse and reorder the test to bind a second time before
releasing the first.

Result:

Test should no longer be flaky.
@PeterAdams-A PeterAdams-A requested a review from dnadoba November 2, 2023 09:18
Copy link
Collaborator

@dnadoba dnadoba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for looking into this!

@simonjbeaumont
Copy link
Collaborator

@swift-server-bot test this please

1 similar comment
@dnadoba
Copy link
Collaborator

dnadoba commented Nov 3, 2023

@swift-server-bot test this please

@dnadoba dnadoba enabled auto-merge (squash) November 3, 2023 13:55
@dnadoba dnadoba merged commit c70e085 into swift-server:main Nov 3, 2023
@gjcairo gjcairo added the semver/none No version bump required. label Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver/none No version bump required.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants