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

Allow running e2e tests as presubmits on GitHub #5918

Open
kwiesmueller opened this issue Jun 30, 2023 · 11 comments
Open

Allow running e2e tests as presubmits on GitHub #5918

kwiesmueller opened this issue Jun 30, 2023 · 11 comments
Assignees
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@kwiesmueller
Copy link
Member

We recently had the case where a PR (#5911) needed to be rolled back because e2e tests were failing.
The author was not able to run the e2e tests and in general I don't think we should rely on people to run e2e tests locally before we accept the code.

I'd propose to move some of our E2E tests into presubmits (https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml) and at least allow to trigger them via bot commands.

This could also allow us to separate CI runs between cluster-autoscaler and VPA as the config allows us to specify which tests to run on which changes.

/good-first-issue
/help

@kwiesmueller kwiesmueller added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 30, 2023
@k8s-ci-robot
Copy link
Contributor

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

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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:

We recently had the case where a PR (#5911) needed to be rolled back because e2e tests were failing.
The author was not able to run the e2e tests and in general I don't think we should rely on people to run e2e tests locally before we accept the code.

I'd propose to move some of our E2E tests into presubmits (https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml) and at least allow to trigger them via bot commands.

This could also allow us to separate CI runs between cluster-autoscaler and VPA as the config allows us to specify which tests to run on which changes.

/good-first-issue
/help

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.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jun 30, 2023
@uroy-personal
Copy link

uroy-personal commented Jul 2, 2023

Hi Kevin,
I am interested to work on this issue. I am trying to retrieve as much details as possible from different links present in this issue. Would be highly obliged if you kindly share more info on this issue. Shall we discuss in slack quickly?

@jbartosik
Copy link
Collaborator

I like the idea

@kwiesmueller
Copy link
Member Author

Feel free to reach out on Slack (kwiesmueller) for more details too.
I only have limited context on the infra side, but #sig-test-infra should be able to help with answers too.
Aside from that I think the config linked above is where the magic happens.

@uroy-personal
Copy link

/assign @uroy-personal

@uroy-personal
Copy link

I like the idea

I like the idea

Thanks @jbartosik !

@uroy-personal
Copy link

uroy-personal commented Jul 19, 2023

Thank you @kwiesmueller , I have observed the differences between these two formats. Hope I will be able to address this change now. As part of this issue how many test cases from https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-config.yaml (it has around 10 test cases ) should I move to https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-autoscaling/sig-autoscaling-presubmits.yaml ( 3 test cases )? . Or shall I just perform a proof of concept with just one test case first. Please advise. Thanks again!

@kwiesmueller
Copy link
Member Author

I think a PoC with one test each (one for VPA, one for Cluster Autoscaler) makes sense before you do all the work for the others. Maybe we can get these submitted fast to try them on real PRs before moving forward with the rest.

@kwiesmueller
Copy link
Member Author

For VPA I'd say let's start with ci-kubernetes-e2e-autoscaling-vpa-full as it's the most comprehensive.
I can't see a test for CA, maybe @mwielgus has a suggestion for a CA test to run on presubmit, otherwise we can only try VPA for now.

@uroy-personal
Copy link

uroy-personal commented Jul 20, 2023

Much appreciated @kwiesmueller ,
I hope to complete ci-kubernetes-e2e-autoscaling-vpa-full in a day or two, raise the PR and liaise with you again. Thanks!

@uroy-personal
Copy link

Hi @kwiesmueller ,
I have raised the PR with changes for the ci-kubernetes-e2e-autoscaling-vpa-full. Need some assistance in the review of this PR : kubernetes/test-infra#30891 . I am following up with the reviewer group.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

4 participants