You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most (if not all) of the Jupyter notebooks that are used to test various components use tenacity for retrying different operations:
Assert that the workload succeeded or is running
Assert that the workload is deleted correctly
The problem with this is that the retry time can vary from machine to machine; very constrained machines, or machines behind a proxy, will take longer to create the task, bring the workload Pod up and running, and run until completion. Because of this, the proposal is to make the retries configurable.
What needs to get done
Identify all the places where tenacity retries are used
Make those retries (either the time limit or number of attempts) configurable, for example, passing a flag to the tox command --retries-limit=<number>
Definition of Done
The UATs have a configuration option for increasing or decreasing the retries time or attempts.
The text was updated successfully, but these errors were encountered:
Context
Most (if not all) of the Jupyter notebooks that are used to test various components use
tenacity
for retrying different operations:The problem with this is that the retry time can vary from machine to machine; very constrained machines, or machines behind a proxy, will take longer to create the task, bring the workload Pod up and running, and run until completion. Because of this, the proposal is to make the retries configurable.
What needs to get done
tenacity
retries are used--retries-limit=<number>
Definition of Done
The UATs have a configuration option for increasing or decreasing the retries time or attempts.
The text was updated successfully, but these errors were encountered: