Skip to content

Wait for the presence server to retire its source after a refused client - #543

Merged
JE-Chen merged 1 commit into
devfrom
fix/presence-server-retire-wait
Nov 2, 2026
Merged

JE-Chen merged 1 commit into
devfrom
fix/presence-server-retire-wait

Conversation

@JE-Chen

@JE-Chen JE-Chen commented Nov 2, 2026

Copy link
Copy Markdown
Member

test_failed_client_thread_start_retires_the_accepted_connection failed on the release PR (#538), on the Windows 3.13 runner. The source had not closed yet: the recorded events were ['reserve', 'construct', 'start'].

Cause. The server drops the accepted connection first and retires its source after that. The test checked for the retirement as soon as the client saw the close, so on a slow runner it ran ahead of the retirement.

Change. The test now waits up to five seconds for the source close and the failed status. It then asserts each one separately.

The server drops the accepted connection and then retires its source. The
test checked for the retirement as soon as the client saw the close, and
on the release PR's Windows 3.13 runner it had not landed yet. It now
waits up to five seconds for both the source close and the failed status.
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@sonarqubecloud

sonarqubecloud Bot commented Nov 2, 2026

Copy link
Copy Markdown

@JE-Chen
JE-Chen merged commit a1a71d0 into dev Nov 2, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant