[Flaky Test] [It] [sig-windows] [Feature:Windows] Eviction [Serial] [Slow] [Disruptive] should evict a pod when a node experiences memory pressure #130419
Description
Which jobs are flaking?
ci-kubernetes-e2e-capz-master-windows-serial-slow
Which tests are flaking?
Kubernetes e2e suite: [It] [sig-windows] [Feature:Windows] Eviction [Serial] [Slow] [Disruptive] should evict a pod when a node experiences memory pressure
Since when has it been flaking?
unsure
Testgrid link
Reason for failure (if possible)
STEP: Scheduling a pod that requests and consumes 500Mi of Memory - k8s.io/kubernetes/test/e2e/windows/eviction.go:104 @ 02/23/25 19:16:29.996
STEP: Scheduling another pod will consume the rest of the node's memory - k8s.io/kubernetes/test/e2e/windows/eviction.go:141 @ 02/23/25 19:16:30.101
I0223 19:16:30.101910 15615 eviction.go:143] Pod2 will consume 55 chunks of 300Mi
STEP: Waiting for pods to start running - k8s.io/kubernetes/test/e2e/windows/eviction.go:174 @ 02/23/25 19:16:30.204
I0223 19:17:06.018178 15615 eviction.go:178] Waiting for pod2 to get evicted
[FAILED] Failure recorded during attempt 1:
Timed out after 600.003s.
Eviction Event was not found
Anything else we need to know?
Relevant SIG(s)
/sig windows