Reduce flakiness of signal handling tests #4247
Draft
Conversation
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
End-to-end tests for signal handling depend on availability of deployments, which may be affected by other running test suites, as is the case of the Fleet agent with pod disruption budgets and priority classes. Therefore, signal handling tests now retry killing a deployment if that deployment or its targeted container is not available.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
End-to-end tests for signal handling depend on availability of deployments, which may be affected by other running test suites, as is the case of the Fleet agent with pod disruption budgets and priority classes.
Therefore, signal handling tests now retry killing a deployment if that deployment or its targeted container is not available.
Refers to #4246.
Additional Information
Checklist
- [ ] I have updated the documentation via a pull request in thefleet-docs repository.