Change:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Previous issues for this suite:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl create quota should create a quota with scopes {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] Pod Disks Should schedule a pod w/ a readonly PD on two hosts, then remove both gracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0644,default) [Conformance] {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] KubeProxy should test kube-proxy [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment RecreateDeployment should delete old pods and create new ones {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should scale a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Services should be able to create a functioning NodePort service {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support port-forward {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] Deployment Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] PrivilegedPod should test privileged pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to create a functioning NodePort service {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to create a functioning NodePort service {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] PrivilegedPod should test privileged pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Cadvisor should be healthy on every node. {Kubernetes e2e suite} Failed: [] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite} Failed: [] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod {Kubernetes e2e suite} Failed: [] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both ungracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] Deployment paused deployment should be ignored by the controller {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should cap back-off at MaxContainerBackOff [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should cap back-off at MaxContainerBackOff [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both ungracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Cadvisor should be healthy on every node. {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment paused deployment should be ignored by the controller {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment paused deployment should be ignored by the controller {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Cadvisor should be healthy on every node. {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should cap back-off at MaxContainerBackOff [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both ungracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both ungracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should cap back-off at MaxContainerBackOff [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should function for intra-pod communication [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Cadvisor should be healthy on every node. {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod {Kubernetes e2e suite} Failed: [] Deployment paused deployment should be ignored by the controller {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] ConfigMap should be consumable from pods in volume as non-root [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should delete a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should apply a new configuration to an existing RC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl patch should add annotations for pods in rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run default should create an rc or deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container with readiness probe should not be ready before initial delay and never restart [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should apply a new configuration to an existing RC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl patch should add annotations for pods in rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run default should create an rc or deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container with readiness probe should not be ready before initial delay and never restart [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should apply a new configuration to an existing RC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl patch should add annotations for pods in rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run default should create an rc or deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container with readiness probe should not be ready before initial delay and never restart [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Monitoring should verify monitoring pods and all cluster nodes are available on influxdb using heapster. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds) {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] V1Job should run a job to completion when tasks sometimes fail and are locally restarted {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should return command exit codes {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid podAffinity is rejected because of the LabelSelectorRequirement is invalid {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support subPath [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. {Kubernetes e2e suite} Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support subPath [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite}
This test flake issue is for the gke continuous soak test to be passing reliably. It is going to be an interesting game of whack a mole, squashing every flake in that suite till I can close this bug. Recent failures seem to be predominantly due to this namespace error: Last three runs 8530, 8531 and 8532 all are due to the same namespace issue.
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support inline execution and attach {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support subPath [Conformance] {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support subPath [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support inline execution and attach {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Monitoring should verify monitoring pods and all cluster nodes are available on influxdb using heapster. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds) {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] V1Job should run a job to completion when tasks sometimes fail and are locally restarted {Kubernetes e2e suite} Failed: [] Kubectl client [] Simple pod should return command exit codes {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid podAffinity is rejected because of the LabelSelectorRequirement is invalid {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
A similar failure in the GCE serial tests was fixed by switching to Debian Node OS.
it's a known issue that docker uses more memory on GCI, and that is being investigated. In this case, the gke build was using containervm (not gci). the problem is that docker v1.11 has a memory leak, and in the soak cluster, the leak will eventually become significant and fail the test. See for more details.
Thanks for the pointers - I will look at the other failures in the GKE soak e2e. tracks the resource usage failures.
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
The bot did not file an issue for this specific failure amongst all the other failures. Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention...
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
We need logs from the server inside the pod - the build logs just print . kubelet/docker logs indicate the pod/container started up fine. Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
New failure with ReplicaSets similar to previous failure with ReplicationControllers - there is some flakiness associated with the test docker to fetch logs from container to find root cause of flakiness.
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
We have had one green run - Jenkins Job - the next run failed again.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Services should be able to change the type and ports of a service [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should have their auto-restart back-off timer reset on image update [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should scale a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should do a rolling update of a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Failed: [] ResourceQuota should verify ResourceQuota with best effort scope. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0777,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] EmptyDir wrapper volumes should becomes running {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu request {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid podAffinity is rejected because of the LabelSelectorRequirement is invalid {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Probing container should be restarted with a exec "cat /tmp/health" liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run pod should create a pod from an image when restart is Never [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl label should update the label on a resource [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Services should create endpoints for unready pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds) {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically: Failed: [] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] ReplicaSet should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] PreStop should call prestop when killing a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks should function for pod communication on a single node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] EmptyDir wrapper volumes should becomes running {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should fail a job [Slow] {Kubernetes e2e suite} Failed: [] ResourceQuota should verify ResourceQuota with best effort scope. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl create quota should reject quota with invalid scopes {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl patch should add annotations for pods in rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run default should create an rc or deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DNS should provide DNS for the cluster [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DNS should provide DNS for pods for Hostname and Subdomain Annotation {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks should function for pod communication between nodes {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume with mappings [Conformance] {Kubernetes e2e suite} Failed: [] Services should check NodePort out-of-range {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] Deployment Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ServiceAccounts should ensure a single API token exists {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API should provide container's and as env vars {Kubernetes e2e suite} Failed: [] Secrets should be consumable from pods in volume [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should preserve source pod IP for traffic thru service cluster IP {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Daemon set [Serial] should run and stop complex daemon {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Secrets should be consumable from pods in env vars [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] HostPath should support r/w {Kubernetes e2e suite} Failed: [] Docker Containers should be able to override the image's default command and arguments [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should run a job to completion when tasks sometimes fail and are not locally restarted {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Sysctls should support unsafe sysctls which are actually whitelisted {Kubernetes e2e suite} Failed: [] Kubectl client [] Simple pod should support inline execution and attach {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support exec {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Port forwarding [] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Mesos starts static pods on every node in the mesos cluster {Kubernetes e2e suite} Failed: [] Generated release12 clientset should create pods, delete pods, watch pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment RecreateDeployment should delete old pods and create new ones {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Daemon set [Serial] should run and stop simple daemon {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Multi-AZ Clusters should spread the pods of a replication controller across zones {Kubernetes e2e suite} Failed: [] Variable Expansion should allow substituting values in a container's args [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should reuse nodePort when apply to an existing SVC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds) {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and ensure its status is promptly calculated. {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy logs on node using proxy subresource [Conformance] {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (non-root,0666,tmpfs) [Conformance] {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl run job should create a job from an image when restart is OnFailure [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should invoke init containers on a RestartAlways pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment RollingUpdateDeployment should scale up and down in the right order {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0666,default) [Conformance] {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a pod. {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ScheduledJob should not schedule new jobs when ForbidConcurrent [Slow] {Kubernetes e2e suite} Failed: [] Pods should be updated [Conformance] {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl expose should create services for rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. {Kubernetes e2e suite} Failed: [] Services should serve a basic endpoint from pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's memory request {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy logs on node [Conformance] {Kubernetes e2e suite} Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and from 3 to 5 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl version should check is all data is printed [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor [Conformance] {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Monitoring should verify monitoring pods and all cluster nodes are available on influxdb using heapster. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollback when there's replica set with no revision {Kubernetes e2e suite} Failed: [] Pods should allow activeDeadlineSeconds to be updated [Conformance] {Kubernetes e2e suite} Failed: [] Variable Expansion should allow substituting values in a container's command [Conformance] {Kubernetes e2e suite} Failed: [] EmptyDir volumes volume on tmpfs should have the correct mode [Conformance] {Kubernetes e2e suite} Failed: [] Job should scale a job up {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ScheduledJob should schedule multiple jobs concurrently {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu request {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a service. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume with mappings and Item mode set[Conformance] {Kubernetes e2e suite} Failed: [] ServiceAccounts should mount an API token into pods [Conformance] {Kubernetes e2e suite} Failed: [] V1Job should run a job to completion when tasks succeed {Kubernetes e2e suite} Failed: [] MetricsGrabber should grab all metrics from a ControllerManager. {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl run rc should create an rc from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SSH should SSH to all nodes and run commands {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Multi-AZ Clusters should spread the pods of a service across zones {Kubernetes e2e suite} Failed: [] Services should use same NodePort with same port but different protocols {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (root,0777,default) [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
I am moving this out of the blocking issues we are tracking for the 1.4 release because the unfinished pieces are non-blockers for the release and do not need to be tracked in the burndown meetings. If there are components besides docs & tests that need to be completed, please move it back to the 1.4 milestone and provide daily status updates.
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid podAffinity is rejected because of the LabelSelectorRequirement is invalid {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0644,tmpfs) [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (non-root,0777,default) [Conformance] {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy to cadvisor [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir wrapper volumes should becomes running {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should set DefaultMode on files [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite}
Last failure was caused by our test framework failure to delete namespace. This looks like a test-infra issue.
Can we mark these resource usage tracking tests as Flaky ? They are not going to pass on GKE because of the Docker memory leak and/or GCI image using more memory. Except for these 3 resource tracking issues, the others have all been intermittent flakes that are already tracked by other issues. Issues about this test specifically:
Also, the bot has attached so many entries to this conversation that this page takes a loong time to load.
Or we can bump the constraints acknowledging the higher usage - current ones seem pretty close.
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Update Demo should do a rolling update of a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] KubeProxy should test kube-proxy [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should be able to override the image's default commmand (docker entrypoint) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Update Demo should do a rolling update of a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] KubeProxy should test kube-proxy [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should be able to override the image's default commmand (docker entrypoint) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Might be related to
https://k8s- Multiple broken tests: Failed: [] KubeProxy should test kube-proxy [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should be able to override the image's default commmand (docker entrypoint) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should do a rolling update of a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if not matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid podAffinity is rejected because of the LabelSelectorRequirement is invalid {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] kubelet [] Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] KubeProxy should test kube-proxy [Slow] {Kubernetes e2e suite} Issues about this test specifically:
Please apply the label to this issue if it does not need to be fixed before we launch 1.4. Otherwise please advise on how to proceed with respect to 1.4.
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should scale a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
We're back to the state when most common failures are caused by 'regular resource usage tracking' for Kubelet -
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl apply should apply a new configuration to an existing RC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Applied the non-release-blocker label because this issue tracks the overall GKE continuous soak suite failures; all failures have issues tracking them individually. As per this issue gets a new attachment when there are more than the threshold of 3 failures in the suite, indicating a test-infra issue. However, there are no generic test-infra issues but rather the number of flakes found in this suite is higher than the threshold.
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] V1Job should scale a job up {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should have monotonically increasing restart count [Conformance] [Slow] {Kubernetes e2e suite}
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] Services should serve a basic endpoint from pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Guestbook application should create and stop a working application [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should create and stop a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DisruptionController evictions: enough pods, absolute =should allow an eviction {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should delete a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Daemon set [Serial] should run and stop simple daemon {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DisruptionController evictions: enough pods, replicaSet, percentage =should allow an eviction {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Failed: [] Networking [] Granular Checks: Services [Slow] should function for endpoint-Service: http {Kubernetes e2e suite} Failed: [] Docker Containers should be able to override the image's default commmand (docker entrypoint) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume with mappings and Item mode set[Conformance] {Kubernetes e2e suite} Failed: [] Probing container should have monotonically increasing restart count [Conformance] [Slow] {Kubernetes e2e suite} Failed: [] DisruptionController should update PodDisruptionBudget status {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should delete a job {Kubernetes e2e suite} Failed: [] Namespaces [Serial] should delete fast enough (90 percent of 100 namespaces in 150 seconds) {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Sysctls should support sysctls {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (root,0666,tmpfs) [Conformance] {Kubernetes e2e suite} Failed: [] Services should use same NodePort with same port but different protocols {Kubernetes e2e suite} Failed: [] Port forwarding [] With a server that expects a client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API should provide pod IP as an env var {Kubernetes e2e suite} Failed: [] ConfigMap should be consumable from pods in volume with mappings [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] KubeletManagedEtcHosts should test kubelet managed /etc/hosts file {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl taint should update the taint on a node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Pods should function for intra-pod communication: http [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl patch should add annotations for pods in rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume with defaultMode set [Conformance] {Kubernetes e2e suite} Failed: [] Deployment deployment should create new pods {Kubernetes e2e suite} Failed: [] Probing container should not be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (non-root,0666,tmpfs) [Conformance] {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a configMap. {Kubernetes e2e suite} Failed: [] Monitoring should verify monitoring pods and all cluster nodes are available on influxdb using heapster. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a pod. {Kubernetes e2e suite} Failed: [] ConfigMap should be consumable in multiple volumes in the same pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Port forwarding [] With a server that expects no client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to change the type and ports of a service [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] Deployment Should scale from 1 pod to 3 pods and from 3 to 5 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Sysctls should not launch unsafe, but not explicitly enabled sysctls on the node {Kubernetes e2e suite} Failed: [] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Slow] {Kubernetes e2e suite} Failed: [] Downward API volume should provide podname only [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 1 pod to 3 pods and from 3 to 5 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should verify ResourceQuota with terminating scopes. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support subPath [Conformance] {Kubernetes e2e suite} Failed: [] Secrets should be consumable from pods in volume with Mode set in the item [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ServiceAccounts should mount an API token into pods [Conformance] {Kubernetes e2e suite} Failed: [] ServiceAccounts should ensure a single API token exists {Kubernetes e2e suite} Issues about this test specifically: Failed: [] PreStop should call prestop when killing a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should do a rolling update of a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should reuse nodePort when apply to an existing SVC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl create quota should create a quota with scopes {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicaSet Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should serve multiport endpoints from pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollback when there's replica set with no revision {Kubernetes e2e suite} Failed: [] V1Job should run a job to completion when tasks sometimes fail and are not locally restarted {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl run job should create a job from an image when restart is OnFailure [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container should be restarted with a /healthz http liveness probe [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that a pod with an invalid NodeAffinity is rejected {Kubernetes e2e suite} Failed: [] Secrets should be consumable from pods in volume [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume as non-root [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should create endpoints for unready pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Update Demo should scale a replication controller [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment RollingUpdateDeployment should delete old pods and create new ones {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should verify ResourceQuota with best effort scope. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should have their auto-restart back-off timer reset on image update [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] LimitRange should create a LimitRange with defaults and ensure pod has those defaults applied. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] kubelet [] Clean up pods on node kubelet should be able to delete 10 pods per node in 1m0s. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that required NodeAffinity setting is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (non-root,0777,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Daemon set [Serial] should run and stop complex daemon with node affinity {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should provide unchanging, static URL paths for kubernetes api services [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should keep restarting failed pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Mesos applies slave attributes as labels {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should get a host IP [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should support rollover {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DisruptionController evictions: too few pods, replicaSet, percentage =should not allow an eviction {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes volume on tmpfs should have the correct mode [Conformance] {Kubernetes e2e suite} Failed: [] Networking [] Granular Checks: Services [Slow] should update endpoints: udp {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl label should update the label on a resource [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support port-forward {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a replication controller. {Kubernetes e2e suite} Failed: [] Secrets should be consumable in multiple volumes in a pod [Conformance] {Kubernetes e2e suite} Failed: [] Pods should allow activeDeadlineSeconds to be updated [Conformance] {Kubernetes e2e suite} Failed: [] Job should scale a job down {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking should check kube-proxy urls {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy logs on node with explicit kubelet port [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide node allocatable (memory) as default memory limit if the limit is not set {Kubernetes e2e suite} Failed: [] Pod Disks should schedule a pod w/ a RW PD, ungracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy logs on node using proxy subresource [Conformance] {Kubernetes e2e suite} Failed: [] Variable Expansion should allow substituting values in a container's command [Conformance] {Kubernetes e2e suite} Failed: [] Sysctls should reject invalid sysctls {Kubernetes e2e suite} Failed: [] Pod Disks Should schedule a pod w/ a RW PD, gracefully remove it, then schedule it on another host [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl create quota should reject quota with invalid scopes {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy to cadvisor using proxy subresource [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Dynamic provisioning [] DynamicProvisioner Alpha should create and delete alpha persistent volumes [Slow] {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy to cadvisor [Conformance] {Kubernetes e2e suite} Failed: [] Pods should support retrieving logs from the container over websockets {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment RollingUpdateDeployment should scale up and down in the right order {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ScheduledJob should not emit unexpected warnings {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should label adopted RSs and pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Pods should function for intra-pod communication: udp [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment deployment should delete old replica sets {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks should schedule a pod w/two RW PDs both mounted to one container, write to PD, verify contents, delete pod, recreate pod, verify contents, and repeat in rapid succession [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should invoke init containers on a RestartAlways pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] PrivilegedPod should test privileged pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for node-Service: udp {Kubernetes e2e suite} Failed: [] Pods should be submitted and removed [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all services are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (root,0644,default) [Conformance] {Kubernetes e2e suite} Failed: [] Downward API volume should provide container's memory request {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should run a job to completion when tasks succeed {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should cap back-off at MaxContainerBackOff [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SSH should SSH to all nodes and run commands {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for node-Service: http {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0777,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON PodAffinity and PodAntiAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (non-root,0644,default) [Conformance] {Kubernetes e2e suite} Failed: [] Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Secrets should be consumable from pods in env vars [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should contain environment variables for services [Conformance] {Kubernetes e2e suite} Failed: [] Job should keep restarting failed pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run deployment should create a deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu request {Kubernetes e2e suite} Failed: [] Downward API volume should set DefaultMode on files [Conformance] {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and from 3 to 1 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] V1Job should fail a job {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Namespaces [Serial] should ensure that all pods are removed when a namespace is deleted. {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl api-versions should check if v1 is in available api versions [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubernetes Dashboard should check that the kubernetes-dashboard instance is alive {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that Inter-pod-Affinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl replace should update a single-container pod's image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should be able to override the image's default command and arguments [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl create quota should create a quota without scopes {Kubernetes e2e suite} Failed: [] DisruptionController evictions: too few pods, absolute =should not allow an eviction {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Secrets should be consumable from pods in volume with defaultMode set [Conformance] {Kubernetes e2e suite} Failed: [] ScheduledJob should not schedule jobs when suspended [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a service. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API should provide container's and as env vars {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that taints-tolerations is respected if matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl cluster-info should check if Kubernetes master services is included in cluster-info [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should run a job to completion when tasks sometimes fail and are not locally restarted {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu limit {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl run default should create an rc or deployment from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should be able to override the image's default arguments (docker cmd) [Conformance] {Kubernetes e2e suite} Failed: [] Rescheduler [Serial] should ensure that critical pod is scheduled in case there is no resources available {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAntiAffinity is respected if matching 2 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Events should be sent by kubelets and the scheduler about pods scheduling and running [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Proxy server should support proxy with --port 0 [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should check NodePort out-of-range {Kubernetes e2e suite} Failed: [] Downward API volume should provide node allocatable (cpu) as default cpu limit if the limit is not set {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl run --rm job should create a job from an image, then delete the job [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment overlapping deployment should not fight with each other {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment paused deployment should be able to scale {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Docker Containers should use the image defaults if command and args are blank [Conformance] {Kubernetes e2e suite} Failed: [] Daemon set [Serial] should run and stop complex daemon {Kubernetes e2e suite} Failed: [] Deployment RecreateDeployment should delete old pods and create new ones {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicaSet should serve a basic image on each replica with a public image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Service endpoints latency should not be very high [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should set mode on item file [Conformance] {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates that embedding the JSON NodeAffinity setting as a string in the annotation value work {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] Deployment Should scale from 5 pods to 3 pods and from 3 to 1 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl logs should be able to retrieve and filter logs [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] MetricsGrabber should grab all metrics from API server. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Probing container with readiness probe should not be ready before initial delay and never restart [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0644,tmpfs) [Conformance] {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy logs on node with explicit kubelet port using proxy subresource [Conformance] {Kubernetes e2e suite} Failed: [] EmptyDir wrapper volumes should not conflict {Kubernetes e2e suite} Issues about this test specifically: Failed: [] InitContainer should not start app containers if init containers fail on a RestartAlways pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment scaled rollout deployment should not block on annotation check {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for pod-Service: udp {Kubernetes e2e suite} Failed: [] Multi-AZ Clusters should spread the pods of a service across zones {Kubernetes e2e suite} Failed: [] Deployment deployment should support rollback {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl apply should apply a new configuration to an existing RC {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Deployment paused deployment should be ignored by the controller {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should prevent NodePort collisions {Kubernetes e2e suite} Issues about this test specifically: Failed: [] NodeProblemDetector [] KernelMonitor should generate node condition and events for corresponding errors {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes volume on default medium should have the correct mode [Conformance] {Kubernetes e2e suite} Failed: [] InitContainer should invoke init containers on a RestartNever pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl expose should create services for rc [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] MetricsGrabber should grab all metrics from a ControllerManager. {Kubernetes e2e suite} Failed: [] Pod Disks should schedule a pod w/ a RW PD shared between multiple containers, write to PD, delete pod, verify contents, and repeat in rapid succession [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support inline execution and attach {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl taint should remove all the taints with the same key off a node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (non-root,0644,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should support r/w {Kubernetes e2e suite} Failed: [] Networking [] Granular Checks: Services [Slow] should function for endpoint-Service: udp {Kubernetes e2e suite} Failed: [] Kubectl client [] Kubectl describe should check if kubectl describe prints relevant information for rc and pods [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ConfigMap should be consumable from pods in volume with mappings as non-root [Conformance] {Kubernetes e2e suite} Failed: [] Kubectl client [] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0777,default) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should provide secure master service [Conformance] {Kubernetes e2e suite} Failed: [] Kubectl client [] Proxy server should support --unix-socket=/path [Conformance] {Kubernetes e2e suite} Failed: [] DNS should provide DNS for pods for Hostname and Subdomain Annotation {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should release NodePorts on delete {Kubernetes e2e suite} Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicaSet Should scale from 1 pod to 3 pods and from 3 to 5 {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should preserve source pod IP for traffic thru service cluster IP {Kubernetes e2e suite} Issues about this test specifically: Failed: [] ReplicationController should serve a basic image on each replica with a private image {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeSelector is respected if matching [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API should provide pod name and namespace as env vars [Conformance] {Kubernetes e2e suite} Failed: [] Pods should be updated [Conformance] {Kubernetes e2e suite} Failed: [] DisruptionController should create a PodDisruptionBudget {Kubernetes e2e suite} Failed: [] ResourceQuota should create a ResourceQuota and capture the life of a persistent volume claim. {Kubernetes e2e suite} Failed: [] Downward API volume should provide container's memory limit {Kubernetes e2e suite} Failed: [] ScheduledJob should schedule multiple jobs concurrently {Kubernetes e2e suite} Issues about this test specifically: Failed: [] HostPath should give a volume the correct mode [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] DNS should provide DNS for ExternalName services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should update annotations on modification [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy logs on node [Conformance] {Kubernetes e2e suite} Failed: [] Services should be able to up and down services {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl run rc should create an rc from an image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Mesos schedules pods annotated with roles on correct slaves {Kubernetes e2e suite} Failed: [] Networking should provide Internet connection for containers [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Variable Expansion should allow substituting values in a container's args [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPod Affinity and AntiAffinity is respected if matching {Kubernetes e2e suite} Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Job should run a job to completion when tasks sometimes fail and are locally restarted {Kubernetes e2e suite} Failed: [] EmptyDir volumes should support (non-root,0666,default) [Conformance] {Kubernetes e2e suite} Failed: [] Kubectl client [] Simple pod should support exec {Kubernetes e2e suite} Issues about this test specifically: Failed: [] MetricsGrabber should grab all metrics from a Kubelet. {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Failed: [] Networking [] Granular Checks: Services [Slow] should update endpoints: http {Kubernetes e2e suite} Failed: [] MetricsGrabber should grab all metrics from a Scheduler. {Kubernetes e2e suite} Failed: [] Pods should support remote command execution over websockets {Kubernetes e2e suite} Failed: [] V1Job should scale a job down {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl rolling-update should support rolling-update to same image [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that NodeAffinity is respected if not matching {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pod Disks should schedule a pod w/ a readonly PD on two hosts, then remove both ungracefully. [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for pod-Service: http {Kubernetes e2e suite} Failed: [] Dynamic provisioning [] DynamicProvisioner should create and delete persistent volumes [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should be able to create a functioning NodePort service {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should return command exit codes {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Port forwarding [] With a server that expects no client request should support a client that connects, sends no data, and disconnects [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] [Serial] [Slow] ReplicationController Should scale from 5 pods to 3 pods and from 3 to 1 and verify decision stability {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for endpoint-Service: http {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: http [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should update nodePort: udp [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor using proxy subresource [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Port forwarding [] With a server that expects a client request should support a client that connects, sends data, and disconnects [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Simple pod should support inline execution and attach {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor [Conformance] {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
I checked one of the nodes , and there were over 4000 goroutines in kubelet. Relevant goroutines: Don't think this happened on GCE, but I haven't checked closely yet. /cc
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy to cadvisor using proxy subresource {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Networking [] Granular Checks: Pods should function for intra-pod communication: udp [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Slow] {Kubernetes e2e suite} Failed: [] Kubectl client [] Simple pod should support exec {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0644,default) [Conformance] {Kubernetes e2e suite} Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (non-root,0644,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for endpoint-Service: udp {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Staging client repo client should create pods, delete pods, watch pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should be submitted and removed [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu limit {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should preserve source pod IP for traffic thru service cluster IP {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (non-root,0644,tmpfs) [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Pods should be submitted and removed [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Services should preserve source pod IP for traffic thru service cluster IP {Kubernetes e2e suite} Issues about this test specifically: Failed: [] [HPA] Horizontal pod autoscaling (scale resource: CPU) [] ReplicationController light Should scale from 2 pods to 1 pod {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Networking [] Granular Checks: Services [Slow] should function for endpoint-Service: udp {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Staging client repo client should create pods, delete pods, watch pods {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Downward API volume should provide container's cpu limit {Kubernetes e2e suite} Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir wrapper volumes should not cause race condition when used for configmaps [Serial] [Slow] {Kubernetes e2e suite} Failed: [] Networking [] Granular Checks: Pods should function for intra-pod communication: udp [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support exec {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates that InterPodAffinity is respected if matching with multiple Affinities {Kubernetes e2e suite} Issues about this test specifically: Failed: [] EmptyDir volumes should support (root,0644,default) [Conformance] {Kubernetes e2e suite}
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates MaxPods limit number of pods that are allowed to run [Slow] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] SchedulerPredicates [Serial] validates resource limits of pods that are allowed to run [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
we need someone to assign this issue to as it's currently failing according to testgrid maybe someone from or has ideas?
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Simple pod should support exec through an HTTP proxy {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy logs on node using proxy subresource [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Proxy version v1 should proxy through a service and a pod [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
The test panic'd because of concurrent map writes. There is a recent change () . could you take a look? Thanks!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
[FLAKE-PING] This flaky-test issue would love to have more attention.
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
Failed: https://k8s- Run so broken it didn't make JUnit output!
thanks for the update
Currently working on fix for concurrent map access failure.
thanks. is also failing fairly frequently with . I'll keep an eye out for a fix.
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
[FLAKE-PING] This flaky-test issue would love to have more attention.
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically:
https://k8s- Multiple broken tests: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 100 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 0 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubelet [Serial] [Slow] [] regular resource usage tracking resource tracking for 35 pods per node {Kubernetes e2e suite} Issues about this test specifically: Failed: [] Kubectl client [] Kubectl should be able to talk to api server kubectl running in a pod could talk to api server [Conformance] {Kubernetes e2e suite} Issues about this test specifically:

Discussion:
"net/http" "os/exec" "strings" <ins> "sync" </ins> "time" "github.com/golang/glog"

func (g *gcpAuthProvider) Login() error { return nil } type cachedTokenSource struct { <ins> lk          sync.Mutex </ins> source      oauth2.TokenSource accessToken string expiry      time.Time

} func (t *cachedTokenSource) Token() (*oauth2.Token, error) { <del> tok := &oauth2.Token{ AccessToken: t.accessToken, TokenType:   "Bearer", Expiry:      t.expiry, } </del> <ins> tok := t.cachedToken() </ins> if tok.Valid() && !tok.Expiry.IsZero() { return tok, nil }

if err != nil { return nil, err } <ins> cache := t.update(tok) </ins> if t.persister != nil { <del> t.cache["access-token"] = tok.AccessToken t.cache["expiry"] = tok.Expiry.Format(time.RFC3339Nano) if err := t.persister.Persist(t.cache); err != nil { </del> <ins> if err := t.persister.Persist(cache); err != nil { </ins> glog.V(4).Infof("Failed to persist token: %v", err) } } return tok, nil } <ins> func (t *cachedTokenSource) cachedToken() *oauth2.Token { t.lk.Lock() defer t.lk.Unlock() return &oauth2.Token{ AccessToken: t.accessToken, TokenType:   "Bearer", Expiry:      t.expiry, } } func (t *cachedTokenSource) update(tok *oauth2.Token) map[string]string { t.lk.Lock() defer t.lk.Unlock() t.accessToken = tok.AccessToken t.expiry = tok.Expiry ret := map[string]string{} for k, v := range t.cache { ret[k] = v } ret["access-token"] = t.accessToken ret["expiry"] = t.expiry.Format(time.RFC3339Nano) return ret } </ins> type commandTokenSource struct { cmd       string args      []string

"fmt" "reflect" "strings" <ins> "sync" </ins> "testing" "time"

} } } <ins> type fakePersister struct { lk    sync.Mutex cache map[string]string } func (f *fakePersister) Persist(cache map[string]string) error { f.lk.Lock() defer f.lk.Unlock() f.cache = map[string]string{} for k, v := range cache { f.cache[k] = v } return nil } func (f *fakePersister) read() map[string]string { ret := map[string]string{} f.lk.Lock() for k, v := range f.cache { ret[k] = v } return ret } type fakeTokenSource struct { token *oauth2.Token err   error } func (f *fakeTokenSource) Token() (*oauth2.Token, error) { return f.token, f.err } func TestCachedTokenSource(t *testing.T) { tok := &oauth2.Token{AccessToken: "fakeaccesstoken"} persister := &fakePersister{} source := &fakeTokenSource{ token: tok, err:   nil, } cache := map[string]string{ "foo": "bar", "baz": "bazinga", } ts, err := newCachedTokenSource("fakeaccesstoken", "", persister, source, cache) if err != nil { t.Fatal(err) } var wg sync.WaitGroup wg.Add(10) for i := 0; i < 10; i++ { go func() { _, err := ts.Token() if err != nil { t.Errorf("unexpected error: %s", err) } wg.Done() }() } wg.Wait() cache["access-token"] = "fakeaccesstoken" cache["expiry"] = tok.Expiry.Format(time.RFC3339Nano) if got := persister.read(); !reflect.DeepEqual(got, cache) { t.Errorf("got cache %v, want %v", got, cache) } } </ins>