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

🐛 ensure etc client generators never return nil #5749

Conversation

fabriziopandini
Copy link
Member

What this PR does / why we need it:
This is a manual cherry-pick of #5710 to the release 0.3 branch.
Note. Code in this branch was slightly different than o main; unfortunately, this version is not unit-testable given that it is not possible to inject a replacement for NewClient.

@k8s-ci-robot k8s-ci-robot added this to the v0.3 milestone Nov 29, 2021
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 29, 2021
@fabriziopandini
Copy link
Member Author

/test pull-cluster-api-e2e-release-full-0-3

@k8s-ci-robot
Copy link
Contributor

@fabriziopandini: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test pull-cluster-api-build-release-0-3
  • /test pull-cluster-api-e2e-release-0-3
  • /test pull-cluster-api-make-release-0-3
  • /test pull-cluster-api-test-release-0-3
  • /test pull-cluster-api-verify-release-0-3

The following commands are available to trigger optional jobs:

  • /test pull-cluster-api-apidiff-release-0-3
  • /test pull-cluster-api-e2e-full-release-0-3

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

  • pull-cluster-api-apidiff-release-0-3
  • pull-cluster-api-build-release-0-3
  • pull-cluster-api-e2e-release-0-3
  • pull-cluster-api-make-release-0-3
  • pull-cluster-api-test-release-0-3
  • pull-cluster-api-verify-release-0-3

In response to this:

/test pull-cluster-api-e2e-release-full-0-3

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.

@fabriziopandini
Copy link
Member Author

/test pull-cluster-api-test-release-0-3

1 similar comment
@fabriziopandini
Copy link
Member Author

/test pull-cluster-api-test-release-0-3

@vincepri
Copy link
Member

/retest

@fabriziopandini
Copy link
Member Author

/test pull-cluster-api-test-release-0-3

@vincepri
Copy link
Member

/retest

@vincepri
Copy link
Member

This seems super unrelated, I wonder if there is a fix we need to apply somehow

@sbueringer
Copy link
Member

sbueringer commented Nov 30, 2021

Based on testgrid I would say it is unrelated: https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-0.3#capi-test-release-0-3

The periodics also almost failed 5x in a row. I wonder if maybe the CI cluster performance is slightly degraded and now we're hitting all the unit test flakes which have already been fixed on main.

@vincepri
Copy link
Member

/approve
/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

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 Nov 30, 2021
@k8s-ci-robot k8s-ci-robot merged commit 57d455f into kubernetes-sigs:release-0.3 Nov 30, 2021
@fabriziopandini fabriziopandini deleted the ensure-etcclientgenerators-never-return-nil branch December 6, 2021 11:53
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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants