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

Reduce e2e replica-restart-policy-tests running time #1319

Closed
Jeffwan opened this issue Jul 31, 2021 · 2 comments
Closed

Reduce e2e replica-restart-policy-tests running time #1319

Jeffwan opened this issue Jul 31, 2021 · 2 comments

Comments

@Jeffwan
Copy link
Member

Jeffwan commented Jul 31, 2021

This is a successful pipeline case. replica-restart-policy-tests takes ~30 mins to finish (rest in parallel tasks take ~5min), cluster creation/deletion takes also takes 30mins. In total, we need ~1hr to pass presubmit e2e test.

image

We could consider to break down replica-restart-policy-tests or increase parallelism inside the tasks to reduce duration of presubmit job.

/good-first-issue
/area testing

@google-oss-robot
Copy link

@Jeffwan:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

This is a successful pipeline case. replica-restart-policy-tests takes ~30 mins to finish (rest in parallel tasks take ~5min), cluster creation/deletion takes also takes 30mins. In total, we need ~1hr to pass presubmit e2e test.

image

We could consider to break down replica-restart-policy-tests or increase parallelism inside the tasks to reduce duration of presubmit job.

/good-first-issue
/area testing

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@stale
Copy link

stale bot commented Mar 2, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Mar 2, 2022
@stale stale bot closed this as completed Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants