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

[release-1.2] 🌱 test/e2e: Cleanup test files #7905

Merged

Conversation

sbueringer
Copy link
Member

Signed-off-by: Stefan Büringer buringerst@vmware.com

What this PR does / why we need it:
Manual cherry-pick of #7825

Might need a few tries to get the tests green. I re-implemented the PR as 1.2 is just too different

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Signed-off-by: Stefan Büringer buringerst@vmware.com
@k8s-ci-robot k8s-ci-robot added this to the v1.2 milestone Jan 11, 2023
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 11, 2023
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 11, 2023
@sbueringer
Copy link
Member Author

/test ?

@k8s-ci-robot
Copy link
Contributor

@sbueringer: The following commands are available to trigger required jobs:

  • /test pull-cluster-api-build-release-1-2
  • /test pull-cluster-api-e2e-release-1-2
  • /test pull-cluster-api-test-mink8s-release-1-2
  • /test pull-cluster-api-test-release-1-2
  • /test pull-cluster-api-verify-release-1-2

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-apidiff-release-1-2
  • /test pull-cluster-api-e2e-full-release-1-2
  • /test pull-cluster-api-e2e-informing-ipv6-release-1-2
  • /test pull-cluster-api-e2e-informing-release-1-2
  • /test pull-cluster-api-e2e-workload-upgrade-1-26-latest-release-1-2

Use /test all to run the following jobs that were automatically triggered:

  • pull-cluster-api-apidiff-release-1-2
  • pull-cluster-api-build-release-1-2
  • pull-cluster-api-e2e-informing-ipv6-release-1-2
  • pull-cluster-api-e2e-informing-release-1-2
  • pull-cluster-api-e2e-release-1-2
  • pull-cluster-api-test-mink8s-release-1-2
  • pull-cluster-api-test-release-1-2
  • pull-cluster-api-verify-release-1-2

In response to this:

/test ?

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.

@sbueringer
Copy link
Member Author

/test pull-cluster-api-e2e-full-release-1-2

@sbueringer
Copy link
Member Author

/test pull-cluster-api-e2e-workload-upgrade-1-26-latest-release-1-2

@fabriziopandini
Copy link
Member

It seems everything worked well. Let's make another round

/test pull-cluster-api-e2e-full-release-1-2
/test pull-cluster-api-e2e-workload-upgrade-1-26-latest-release-1-2

@sbueringer
Copy link
Member Author

Looks like an unrelated flake
/retest

@sbueringer
Copy link
Member Author

@fabriziopandini should be good to go

@fabriziopandini
Copy link
Member

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 12, 2023
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 46903fd4c401abf0cb0126f2a4cf7f0b94daa0d9

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 12, 2023
@k8s-ci-robot k8s-ci-robot merged commit c3fff18 into kubernetes-sigs:release-1.2 Jan 12, 2023
@sbueringer sbueringer deleted the pr-cleanup-testfiles-1.2 branch January 12, 2023 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants