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
There are a few things we could do to make tests complete faster:
eliminate the log aggregator and expose an service on the operator directly
wait for flows to be active before checking for results
wait for simulation pods to be in a running state
Right now we wait a set period of time for tests to complete. Given we do not have insights into the state of the flows we have to allow time for the flows to activate and the simulation pods to start. If we watch the pods and flows and wait for them to become active we can assume it should only take at most 1 flush interval configured in the test output. We might want to pad with a little extra room to allow time for requests to complete but this would mean our fixed delay would fall from 5 minutes to 2 seconds. Tests would still need to wait for all the resources to be ready but this is typically less than 5m right now.
The text was updated successfully, but these errors were encountered:
There are a few things we could do to make tests complete faster:
Right now we wait a set period of time for tests to complete. Given we do not have insights into the state of the flows we have to allow time for the flows to activate and the simulation pods to start. If we watch the pods and flows and wait for them to become active we can assume it should only take at most 1 flush interval configured in the test output. We might want to pad with a little extra room to allow time for requests to complete but this would mean our fixed delay would fall from 5 minutes to 2 seconds. Tests would still need to wait for all the resources to be ready but this is typically less than 5m right now.
The text was updated successfully, but these errors were encountered: