kubernetes: [k8s.io] MemoryEviction [Slow] [Serial] [Disruptive] when there is memory pressure should evict pods in the correct order (besteffort first, then burstable, then guaranteed) {E2eNode Suite}

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubelet-serial-gce-e2e-ci/489/

Failed: [k8s.io] MemoryEviction [Slow] [Serial] [Disruptive] when there is memory pressure should evict pods in the correct order (besteffort first, then burstable, then guaranteed) {E2eNode Suite}

/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e_node/memory_eviction_test.go:163
Expected error:
    <*errors.errorString | 0xc8200bdad0>: {
        s: "pod ran to completion",
    }
    pod ran to completion
not to have occurred
/var/lib/jenkins/workspace/kubelet-serial-gce-e2e-ci/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:57

Previous issues for this test: #31582

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 119 (119 by maintainers)

Commits related to this issue

Most upvoted comments

hey bot this issue got most of my attention on Friday and will get more this week

On Tuesday, September 6, 2016, Kubernetes Submit Queue < notifications@github.com> wrote:

[FLAKE-PING] @aveshagarwal https://github.com/aveshagarwal @derekwaynecarr https://github.com/derekwaynecarr @mtaufen https://github.com/mtaufen @vishh https://github.com/vishh

This flaky-test issue would love to have more attention.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kubernetes/kubernetes/issues/31676#issuecomment-245114915, or mute the thread https://github.com/notifications/unsubscribe-auth/AF8dbAJnj9E5kA3pDwQy1_5vsSpFNIbLks5qnegCgaJpZM4JwKRT .