Skip to content

Stabilize resilience reload ownership test - #16

Open
remdui wants to merge 4 commits into
mainfrom
fix/resilience-reload-test-race
Open

Stabilize resilience reload ownership test#16
remdui wants to merge 4 commits into
mainfrom
fix/resilience-reload-test-race

Conversation

@remdui

@remdui remdui commented Jul 27, 2026

Copy link
Copy Markdown
Member

Root cause

reloadConfiguration() deliberately starts a non-blocking health refresh. The concurrency test took its probe-count baseline immediately afterward, so it could observe the in-flight probe after the increment but before its future completed. The later explicit refresh then reused that same future, making the test incorrectly conclude that the replacement resilience registration had been removed.

Fix

Drain the reload-triggered health request before recording the baseline. Closing the old slot then happens after a completed baseline probe, and the final explicit request must exercise the replacement runtime control.

Scope

This is test synchronization only. Production reload behavior remains non-blocking, and the ownership invariant being tested is unchanged.

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