kubernetes: [Failing Test] gce-windows-1909-master (ci-kubernetes-e2e-windows-gce-1909)
Which jobs are failing:
gce-windows-1909-master (ci-kubernetes-e2e-windows-gce-1909)
Since when has it been failing:
5th March
Testgrid link: https://testgrid.k8s.io/sig-release-master-informing#gce-windows-1909-master
Reason for failure: Many test cases are stale and others are failing. It seems that the jobs are completely broken.
Anything else we need to know: /priority critical-urgent /milestone v1.18 /sig windows /cc @kubernetes/sig-windows-bugs /cc @kubernetes/ci-signal
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 37 (33 by maintainers)
Yes I am working on a fix https://github.com/kubernetes/kubernetes/pull/96294
Monitoring and will close if we see successful runs after merge of https://github.com/kubernetes/test-infra/pull/18435
Yes this looks to be the same as in #87389. I am looking into it now
Hi @hasheddan, yes we are getting value from
gce-windows-1909-masterandgce-windows-2019-master. For each test job it looks like there are currently four tests that are consistently failing, and other tests are flaking occasionally. This is certainly a useful signal to tell us “things are stable, nothing major is broken.” When something major was wrong, we fixed it.It would be great if we could fix those four currently-failing tests. I regret that we’ve been unable to do that, and I apologize for being unresponsive here. Our team is struggling with staffing due to health issues and the general disruption over the last several months. Thank you for your understanding.
We’ll try to at least maintain the current level of green-ness. If the failing test jobs are a burden for you and your team, then please move them off the
master-informingdashboard or do whatever makes sense.Yes, I’ll try to take a look this week.