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
Currently even when running in sequential mode some tests will time out randomly. This indicates that the environment the e2e tests run in does not have adequate resources.
The github action environment either needs more CPU / memory / etc, or perhaps the action needs to create a separate github environment that can be used to run the tests with more resources. Ideally we should have enough resources in the CI e2e test environment to run the tests in parallel without random timeout failures.
The text was updated successfully, but these errors were encountered:
In fact ideally this e2e environment should mirror the prod environment as much as we are able, though obviously it will not be at the same scale as prod.
Terms
Behavior
Currently even when running in sequential mode some tests will time out randomly. This indicates that the environment the e2e tests run in does not have adequate resources.
The github action environment either needs more CPU / memory / etc, or perhaps the action needs to create a separate github environment that can be used to run the tests with more resources. Ideally we should have enough resources in the CI e2e test environment to run the tests in parallel without random timeout failures.
The text was updated successfully, but these errors were encountered: