Skip to content
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

Configure eventually timeouts in e2e tests #2935

Merged
merged 1 commit into from
Oct 16, 2023

Conversation

georgethebeatle
Copy link
Member

Is there a related GitHub Issue?

No

What is this change about?

Instead of specifying cutom timeouts in Eventually, configure the
default eventually timeout and polling interval consistently across
e2e suites.

Tag your pair, your PM, and/or team

@danail-branekov

@danail-branekov danail-branekov enabled auto-merge (rebase) October 12, 2023 09:18
@danail-branekov danail-branekov changed the title y Configure eventually timeouts in e2e tests Oct 12, 2023
@georgethebeatle georgethebeatle force-pushed the configure-test-timeouts branch from 243b4c6 to ad386f0 Compare October 13, 2023 08:37
@danail-branekov danail-branekov force-pushed the configure-test-timeouts branch 2 times, most recently from 9f24580 to 505c548 Compare October 16, 2023 08:54
Instead of specifying cutom timeouts in `Eventually`, configure the
default eventually timeout and polling interval consistently across
e2e suites.

Also, cf/kubectl utilities wait for the `gexec.Session` to exit so that
tests can check the exit code directly without `Eventually` or explicit
waits.

Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
@danail-branekov danail-branekov force-pushed the configure-test-timeouts branch from 505c548 to db33498 Compare October 16, 2023 10:08
@danail-branekov danail-branekov merged commit 5fe27ef into main Oct 16, 2023
7 checks passed
@danail-branekov danail-branekov deleted the configure-test-timeouts branch October 16, 2023 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants