Add an additional retry for timing out tests #53159
Merged
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the retry mechanism for timing out tests by increasing the retry count from 1 to 2 additional attempts and improving the error messaging structure. The change aims to reduce test flakiness by providing more opportunities for transient timeout issues to resolve.
- Increases retry attempts from 1 to 2 for timing out tests
- Refactors timeout handling into a dedicated method for better code organization
- Improves error messaging to provide detailed information about all retry attempts
jsquire
approved these changes
Oct 10, 2025
Member
Author
|
@microsoft-github-policy-service rerun |
jsquire
approved these changes
Oct 11, 2025
Member
Author
|
/check-enforcer evaluate |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.