-
Notifications
You must be signed in to change notification settings - Fork 38.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
EC2 + GCE GPU CI Jobs not running any test cases #124950
Comments
Note that while the job is "green" after kubernetes/test-infra#32635 we are not running This issue is a sub-variant of kubernetes/test-infra#32242 |
/remove-sig k8s-infra |
It's not, see above #124950 (comment) The |
I don't even seen The only matching test is for windows ... asking if something changed with the test cases in SIG Node slack |
The test cases were all deleted ... bf268f0#diff-7629c065680da0396ef2e8d190ce7cdd1dbf2c336f99c22ec543a4be61d74ccd |
NOTE: This also impacts the EC2 Job which is no longer running any test cases. The GCE job is running and "passing" same as the ec2 job now ... neither of which run any tests. /retitle EC2 + GCE GPU CI Jobs not running any test cases See an old run: https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-ec2-device-plugin-gpu/1781225142752382976 (ran: Current: (7 "tests" passed, none of which are actual e2e tests) |
😅 |
Yes, I think the job is coming up but not the driver install or device plugin. We need to add more log dump there, I've been discussing a bit with dims what we should do about the test removal in #sig-node: https://kubernetes.slack.com/archives/C0BP8PW9G/p1716914276819719?thread_ts=1716913485.823089&cid=C0BP8PW9G |
Talked to @elfinhe this morning about the driver install. |
FYI #122828 documents that |
Which jobs are failing?
master-blocking
Which tests are failing?
kubetest.Up
Since when has it been failing?
05/17
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#gce-device-plugin-gpu-master
Reason for failure (if possible)
Anything else we need to know?
No response
Relevant SIG(s)
/sig k8s-infra
The text was updated successfully, but these errors were encountered: