- Notifications
You must be signed in to change notification settings - Fork928
chore: tweak e2e test timeouts#15275
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Is there a particular reason this is still in Draft? Looks good to me as a short term tweak. Drive by comment only vaguely related to this PR (non-blocking): I think we should be treating timeouts as first class test criteria as opposed something we tweak to handle flakes. That said, I'm aware the test execution environment makes all the difference. |
Uh oh!
There was an error while loading.Please reload this page.
because I forgor to hit "ready" lol |
85ff8e0
intomainUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Closescoder/internal#178
tweak some timeouts for slow tests/operations to be more targeted, so that we can make the generic timeout shorterand reduce the number of flakes caused by timeouts on the long running/slow tests.