Which jobs are flaking?

• ci-crio-cgroupv2-node-e2e-eviction
• ci-crio-cgroupv1-node-e2e-eviction
  also
• pull-crio-cgroupv1-node-e2e-eviction
• pull-crio-cgroupv2-node-e2e-eviction

https://storage.googleapis.com/k8s-triage/index.html?test=PodAndContainerStatsFromCRI

Which tests are flaking?

when we run containers with PodAndContainerStatsFromCRI=true or false.

• It] [sig-node] PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive] [NodeFeature:Eviction] when we run containers with PodAndContainerStatsFromCRI=true that should cause PIDPressure should eventually evict all of the correct pods
• E2eNode Suite.[It] [sig-node] PriorityPidEvictionOrdering [Slow] [Serial] [Disruptive] [NodeFeature:Eviction] when we run containers with PodAndContainerStatsFromCRI=false that should cause PIDPressure should eventually evict all of the correct pods

Since when has it been flaking?

years ago: #107804

Testgrid link

https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-node-e2e-eviction and https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv2-node-e2e-eviction

Reason for failure (if possible)

STEP: checking eviction ordering and ensuring important pods don't fail - k8s.io/kubernetes/test/e2e_node/eviction_test.go:770 @ 10/10/24 16:06:49.933
[FAILED] pod fork-bomb-container-with-high-priority-pod failed; expected Status.Reason to be Evicted, but got 
Expected
    <string>: 
to equal
    <string>: Evicted
In [It] at: k8s.io/kubernetes/test/e2e_node/eviction_test.go:803 @ 10/10/24 16:06:49.934
< Exit [It] should eventually evict all of the correct pods - k8s.io/kubernetes/test/e2e_node/eviction_test.go:628 @ 10/10/24 16:06:49.934 (56.174s)
> Enter [AfterEach] TOP-LEVEL - k8s.io/kubernetes/test/e2e_node/eviction_test.go:690 @ 10/10/24 16:06:49.934
STEP: deleting pods - k8s.io/kubernetes/test/e2e_node/eviction_test.go:701 @ 10/10/24 16:06:49.934

Anything else we need to know?

No response

Relevant SIG(s)

/sig node