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

[PR] Improve the stability of e2e tests #149

Closed
kopf-archiver bot opened this issue Aug 18, 2020 · 0 comments
Closed

[PR] Improve the stability of e2e tests #149

kopf-archiver bot opened this issue Aug 18, 2020 · 0 comments
Labels
archive automation CI/CD: testing, linting, releasing automatically

Comments

@kopf-archiver
Copy link

kopf-archiver bot commented Aug 18, 2020

A pull request by nolar at 2019-07-15 00:43:49+00:00
Original URL: zalando-incubator/kopf#149
Merged by nolar at 2019-07-16 09:57:55+00:00

Part of an effort to make Kopf-based operators more stable and resilient.

Issue : #13 #142

Description

E2E tests are flaky and unstable. This PR makes them more stable by:

  • Running in a standalone mode (on the same minikube as other, probably failed tests — to prevent freezing for minutes).
  • Limiting a time of termination of a background operator to 60s (and adding this feature).
  • Using a dynamic pod name in the pod-involving e2e tests (otherwise, it hits "409 Conflict" — when the pod already exists in the same cluster (actual for the local runs)).

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • Refactor/improvements
@kopf-archiver kopf-archiver bot closed this as completed Aug 18, 2020
@kopf-archiver kopf-archiver bot changed the title [archival placeholder] [PR] Improve the stability of e2e tests Aug 19, 2020
@kopf-archiver kopf-archiver bot added the automation CI/CD: testing, linting, releasing automatically label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archive automation CI/CD: testing, linting, releasing automatically
Projects
None yet
Development

No branches or pull requests

0 participants