-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Introduce etcd unit and integration tests jobs for ppc64le architecture #34543
Conversation
@@ -467,6 +498,38 @@ periodics: | |||
cpu: "2" | |||
memory: "3Gi" | |||
|
|||
- name: ci-etcd-integration-1-cpu-ppc64le |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: should we add nodeSelector? I see some job have it, but some not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ahrtr, currently, the k8s-infra-ppc64le-prow-build
cluster consists of ppc64le nodes only. I've removed the nodeSelector
section for uniformity for the jobs that run on k8s-infra-ppc64le-prow-build
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx for the clarification.
7246c91
to
f40d5fe
Compare
/lgtm /hold for other maintainers to review |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahrtr, kishen-v 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 |
cc @BenTheElder |
[discussed in sig-etcd meeting, deferring to etcd maintainers but there are no concerns from a test-infra perspective, this only costs us pulling the images on the other budgets and I think having periodic release signal for platforms you support is good] |
@ahrtr can you please tag the person who is missing here?
|
/cc @jmhbnz @serathius @fuweid |
@ivanvc: GitHub didn't allow me to request PR reviews from the following users: fuweid. Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
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-sigs/prow repository. |
/lgtm |
I see 4/5 approvals have been acked this PR, hence removing the hold. |
@kishen-v: Updated the
In response to this:
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-sigs/prow repository. |
I see all the four tests ran and passed successfully, thanks @kishen-v |
Add prow job configurations to run integration and unit tests periodically against the main branch on the
k8s-infra-ppc64le-prow-build
cluster.The e2e tests on the ppc64le architecture was added through: #34503