-
Notifications
You must be signed in to change notification settings - Fork 496
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
[release/8.0] [tests] Use ResiliencePipeline in IntegrationTests #3623
Conversation
.. with a policy to retry with 1 sec delays, and a total timeout of 90 secs on the service side. The test(client) side has an overall http request timeout for 120 secs which would allow the real errors from the service to get surfaced to the client.
…han one resource is given
https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1305 ``` dotnet_diagnostic.CA1305.severity = none ``` Addresses review feedback from @ eerhardt .
As I understand it, the polly change is purely moving to the newer polly API, so build validation is perhaps sufficient. The rest is test only changes. |
Yeah we used this opportunity to reduce our dependencies to just Polly.core and Polly.extensions. The full Polly is not needed. Removing the dependency later might be considered a breaking change. Since it builds and tests pass there shouldn’t be any risk. |
Backport of #3385 to release/8.0
/cc @radical
Customer Impact
Testing
Risk
Regression?
Microsoft Reviewers: Open in CodeFlow