Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate Server discovery failure in an extra test #236

Merged
merged 1 commit into from
Feb 12, 2025

Conversation

Nuckal777
Copy link
Contributor

Proposed Changes

Until a Server becomes Available it is consistently changing between the Initial and Discovery state. Thus every check against a Servers state after an initial check for Initial and before a sucessful Available check is racy. The raciness is reduced by validating discovery failure in a dedicated test.

Until a Server becomes Available it is consistently
changing between the Initial and Discovery state.
Thus every check against a Servers state
after an initial check for Initial and before a
sucessfull Available check is racy. The raciness
is reduced by validating discovery failure in a
dedicated test.
@Nuckal777 Nuckal777 force-pushed the test-validate-discovery-failure branch from 4aef311 to a5db086 Compare February 12, 2025 18:58
@afritzler afritzler added the enhancement New feature or request label Feb 12, 2025
@afritzler afritzler merged commit 94f63c0 into main Feb 12, 2025
10 checks passed
@afritzler afritzler deleted the test-validate-discovery-failure branch February 12, 2025 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants