This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 49 succeeded
Started2020-10-21 02:56
Elapsed4h26m
Revision
Builderedec95f6-1348-11eb-a3c5-629ea79d0103
infra-commit5c86f7035
job-versionv1.17.14-rc.0.7+a70c45e3b1926e
repok8s.io/kubernetes
repo-commita70c45e3b1926e789f680e3073a0d37a117cd36d
repos{u'k8s.io/kubernetes': u'release-1.17'}
revisionv1.17.14-rc.0.7+a70c45e3b1926e

Test Failures


E2eNode Suite [k8s.io] Container Manager Misc [Serial] Validate OOM score adjustments [NodeFeature:OOMScoreAdj] once the node is setup container runtime's oom-score-adj should be -999 5m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sContainer\sManager\sMisc\s\[Serial\]\sValidate\sOOM\sscore\sadjustments\s\[NodeFeature\:OOMScoreAdj\]\sonce\sthe\snode\sis\ssetup\scontainer\sruntime\'s\soom\-score\-adj\sshould\sbe\s\-999$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/container_manager_test.go:80
Timed out after 300.000s.
Expected
    <*errors.errorString | 0xc0008186f0>: {
        s: "expected pid 32554's oom_score_adj to be -999; found -500",
    }
to be nil
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/container_manager_test.go:86
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-1-15-v20200824_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [k8s.io] CriticalPod [Serial] [Disruptive] [NodeFeature:CriticalPod] when we need to admit a critical pod should be able to create and delete a critical pod 0.07s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sCriticalPod\s\[Serial\]\s\[Disruptive\]\s\[NodeFeature\:CriticalPod\]\swhen\swe\sneed\sto\sadmit\sa\scritical\spod\sshould\sbe\sable\sto\screate\sand\sdelete\sa\scritical\spod$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/critical_pod_test.go:55
failed to create PriorityClasses with an error: PriorityClass.scheduling.k8s.io "critical-pod-test-high-priority" is invalid: value: Forbidden: maximum allowed value of a user defined priority is 1000000000
Expected
    <bool>: false
to be true
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/critical_pod_test.go:89
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-1-15-v20200824_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [k8s.io] InodeEviction [Slow] [Serial] [Disruptive][NodeFeature:Eviction] when we run containers that should cause DiskPressure should eventually evict all of the correct pods 16m50s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sInodeEviction\s\[Slow\]\s\[Serial\]\s\[Disruptive\]\[NodeFeature\:Eviction\]\swhen\swe\srun\scontainers\sthat\sshould\scause\sDiskPressure\s\sshould\seventually\sevict\sall\sof\sthe\scorrect\spods$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/eviction_test.go:522
Oct 21 03:36:06.366: Failed to delete pod "innocent-pod": etcdserver: request timed out
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:151
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-1-15-v20200824_01.xml

Find innocent-pod mentions in log files | View test history on testgrid


Node Tests 4h23m

error during go run /go/src/k8s.io/kubernetes/test/e2e_node/runner/remote/run_remote.go --cleanup --logtostderr --vmodule=*=4 --ssh-env=gce --results-dir=/workspace/_artifacts --project=ubuntu-image-validation --zone=us-west1-b --ssh-user=prow --ssh-key=/workspace/.ssh/google_compute_engine --ginkgo-flags=--nodes=1 --focus="\[Serial\]" --skip="\[Flaky\]|\[Benchmark\]|\[NodeAlphaFeature:.+\]" --test_args=--feature-gates=DynamicKubeletConfig=true --test-timeout=5h0m0s --images=ubuntu-gke-1804-1-15-v20200824 --image-project=ubuntu-os-gke-cloud-devel: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 49 Passed Tests

Show 267 Skipped Tests