-
Notifications
You must be signed in to change notification settings - Fork 562
Updating tests to retry after initial if failed #5094
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
base: main
Are you sure you want to change the base?
Conversation
…ansient runtime errors flakyness
… failure, host failure or task failure handling
|
|
||
| if (maxRetries <= 1) | ||
| { | ||
| return new[] { new XunitTestCase(_diagnosticMessageSink, discoveryOptions.MethodDisplayOrDefault(), discoveryOptions.MethodDisplayOptionsOrDefault(), testMethod) }; |
Check warning
Code scanning / CodeQL
Missing Dispose call on local IDisposable Warning
Copilot Autofix
AI about 2 months ago
Copilot could not generate an autofix suggestion
Copilot could not generate an autofix suggestion for this alert. Try pushing a new commit or if the problem persists contact support.
Updated SqlServerFhirDataStore to properly handle max retries and cap at 100.
Adding timing around each await call
Description
This PR introduces retries to Unit test, Integration and E2E tests to reduce need to manually retry if transient errors occurring during execution of tests.
Related issues
Addresses AB#166378.
Testing
Describe how this change was tested.
Ran PR against local users branch
FHIR Team Checklist
Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)