-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Node testgrid dashboard cleanup #23231
Comments
/assign |
Here is the list of all tabs (sorted):
Not sure which ones could be merged... |
|
Also should we also think about removing windows jobs from |
Agree with both... @ehashman wdyt? |
/cc @SergeyKanzhelev |
the idea of critical tab was a stepping stone to promote to release blocking as far as I remember. It didin't work as was intended I'd vote for removing windows from containerd. But let's ping @marosset on the PR |
Thanks for letting us know about this!! for now lets keep it as it is.
for windows, lets wait for @marosset feedback |
I'm OK with removing the windows tabs from Since these are GCE jobs I'd like either @pjh or @ibabou to ACK this too |
I'm okay with removing the windows tabs from there. ACK. Having those as part of sig-windows-gce & sig-windows-*-release is sufficient. |
+1, removing those Windows jobs from |
Thanks for the inputs from windows team, Now we have two items that need PR
you can use this https://cs.k8s.io/?q=node-kubelet-master&i=nope&files=&excludeFiles=&repos=kubernetes/test-infra to search for jobs and dashboard. |
I can work on with the PR regarding removing windows jobs from containerd dasboard |
Hey @adisky I can work on the second item (move double listed jobs to ensure they are filed in the right place). |
@Debanitrkl @rayandas Thanks for taking this up |
/assign |
/assign |
Not sure we're done yet... |
@matthyx: Reopened this issue. 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. |
Can someone please suggest the right place to have the This test grid seems essential to track k8s unit test failures on ppc64le. |
|
not sure either, wondering if we can add to some of the periodic jobs run(don't really know where are they??), worst case - lets create a new group called |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
both remaining PRs are merged |
@matthyx: Closing this issue. 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. |
What should be cleaned up or changed:
As discussed in the SIG Node CI Subproject meeting today and last week, our testgrid dashboards are a bit of a mess:
Here is our cleanup plan:
pr-*
jobs across various tabs into a newsig-node-presubmits
tabsig-node-containerd
andsig-node-containerd-io
)sig-node-release-blocking
and don't also need to be included undersig-node-kubelet
)Provide any links for context:
https://testgrid.k8s.io/sig-node-kubelet#node-kubelet-features-master
/cc @adisky @matthyx @ipochi
/sig node
The text was updated successfully, but these errors were encountered: