-
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
drop gcp-project-type from presubmits #30789
drop gcp-project-type from presubmits #30789
Conversation
what are those failures? |
I was getting
I see logs mention the node-e2e-project but we don't have that project in any of our other presubmits. |
/assign @BenTheElder it may be related indeed, but not completely familiar with this setup |
/assign @SergeyKanzhelev |
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.
Can you move these jobs to the community cluster?
You can do this by adding the field cluster: k8s-infra-prow-build
to the job
xref #29722
/retest |
bfbcfe6
to
3d7fbf6
Compare
/retest |
does this needs to be rebased now? I am not sure I understand all the differences between projects, but this PR seems incomplete with one job adding cluster and others don't |
I rebased earlier today. I only saw one job in the presubmits that was missing the cluster so I added that. And the I was told that the gcp-project-type may not be required for the presubmits (#sig-testing help mostly). |
@@ -1134,6 +1134,7 @@ presubmits: | |||
- '--test-args=--container-runtime-endpoint=unix:///var/run/crio/crio.sock --container-runtime-process-name=/usr/local/bin/crio --container-runtime-pid-file= --kubelet-flags="--cgroup-driver=systemd --cgroups-per-qos=true --cgroup-root=/ --runtime-cgroups=/system.slice/crio.service --kubelet-cgroups=/system.slice/kubelet.service" --extra-log="{\"name\": \"crio.log\", \"journalctl\": [\"-u\", \"crio\"]}"' | |||
- --image-config-file=/home/prow/go/src/k8s.io/test-infra/jobs/e2e_node/crio/latest/image-config-cgrpv2-k8s-infra-prow-build-kubetest2.yaml | |||
- name: pull-crio-cgroupv1-node-e2e-features | |||
cluster: k8s-infra-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.
This is the only job that was missing a cluster tag. All other presubmits have a cluster so they have already been migrated to the community cluster.
@@ -1161,7 +1162,6 @@ presubmits: | |||
args: | |||
- --deployment=node | |||
- --env=KUBE_SSH_USER=core | |||
- --gcp-project-type=node-e2e-project |
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.
Not entirely sure why but it seems that presubmits don't require this project-type.
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kannon92, SergeyKanzhelev 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 |
@kannon92: 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/test-infra repository. |
Moving these periodics to presubmits. I notice that in the presubmit file we don't have gcp-project-type.
Seeing failures in https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/120679/pull-crio-cgroupv1-node-e2e-eviction/1704873947100614656/