-
Notifications
You must be signed in to change notification settings - Fork 36
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
Retry deprovisioning integ test on 202 return #457
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #457 +/- ##
============================================
- Coverage 71.88% 71.72% -0.16%
+ Complexity 620 619 -1
============================================
Files 78 78
Lines 3126 3126
Branches 236 236
============================================
- Hits 2247 2242 -5
- Misses 772 776 +4
- Partials 107 108 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Daniel Widdis <[email protected]>
5894a34
to
5478fa0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved but can we also add this deprovision check for all the model deployment tests
I think we only need to "test" the deprovisioning once. If you want to just always execute the |
Retry deprovisioning on 202 return Signed-off-by: Daniel Widdis <[email protected]> (cherry picked from commit f4fa29e) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Retry deprovisioning integ test on 202 return (#457) Retry deprovisioning on 202 return (cherry picked from commit f4fa29e) Signed-off-by: Daniel Widdis <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
By design, the deprovision API makes a best effort at deprovisioning. Some deprovisioning may take longer than twice the 1 second delay between retries, which results in a 202 error to the user indicating which resources were not deprovisioned (yet). Rerunning the API in this case works after a few more seconds.
Updating the deprovisioning test to do a wait-and-retry in this edge case (which seems to happen on macOS frequently and Windows rarely).
Issues Resolved
Fixes the most recent flaky tests
https://github.com/opensearch-project/flow-framework/actions/runs/7659934815
https://github.com/opensearch-project/flow-framework/actions/runs/7659475132
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.