This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 137 succeeded
Started2021-09-23 16:50
Elapsed3h11m
Revision
Builder61a59d8a-1c8e-11ec-883b-c61df66c07e7
infra-commitfef59c14e
job-versionv1.23.0-alpha.2.190+6c2f644482c018
kubetest-version
repok8s.io/kubernetes
repo-commit6c2f644482c018cd6650ef64ee300a5759366b70
repos{u'k8s.io/kubernetes': u'master'}
revisionv1.23.0-alpha.2.190+6c2f644482c018

Test Failures


E2eNode Suite [sig-node] Dockershim [Serial] [Disruptive] [Feature:Docker][Legacy:Docker] should clean up pod sandbox checkpoint after pod deletion 3m6s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sDockershim\s\[Serial\]\s\[Disruptive\]\s\[Feature\:Docker\]\[Legacy\:Docker\]\sshould\sclean\sup\spod\ssandbox\scheckpoint\safter\spod\sdeletion$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/dockershim_checkpoint_test.go:55
Sep 23 18:06:57.281: Failed to observe checkpoint being removed within timeout: timed out waiting for the condition
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/dockershim_checkpoint_test.go:57
				
				Click to see stdout/stderrfrom junit_ubuntu_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Memory Manager [Serial] [Feature:MemoryManager] with static policy when guaranteed pod has init and app containers should succeed to start the pod 1m5s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sMemory\sManager\s\[Serial\]\s\[Feature\:MemoryManager\]\swith\sstatic\spolicy\swhen\sguaranteed\spod\shas\sinit\sand\sapp\scontainers\sshould\ssucceed\sto\sstart\sthe\spod$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/memory_manager_test.go:327
Found more than one kubelet service running: "0 loaded units listed. Pass --all to see loaded but inactive units, too.\nTo show all installed unit files use 'systemctl list-unit-files'.\n"
Expected
    <int>: 0
not to equal
    <int>: 0
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/util.go:411
				
				Click to see stdout/stderrfrom junit_cos-stable2_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] Restart [Serial] [Slow] [Disruptive] [NodeFeature:ContainerRuntimeRestart] Container Runtime Network should recover from ip leak 13m39s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sRestart\s\[Serial\]\s\[Slow\]\s\[Disruptive\]\s\[NodeFeature\:ContainerRuntimeRestart\]\sContainer\sRuntime\sNetwork\sshould\srecover\sfrom\sip\sleak$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/restart_test.go:85
Unexpected error:
    <*errors.errorString | 0xc0002deca0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_collector.go:384
				
				Click to see stdout/stderrfrom junit_ubuntu_01.xml

Filter through log files | View test history on testgrid


kubetest Node Tests 3h9m

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=k8s-jkns-gke-ubuntu-reboot --zone=us-west1-b --ssh-user=prow --ssh-key=/workspace/.ssh/google_compute_engine --ginkgo-flags=--nodes=1 --focus="\[Serial\]" --skip="\[Flaky\]|\[Benchmark\]|\[NodeSpecialFeature:.+\]|\[NodeSpecialFeature\]|\[NodeAlphaFeature:.+\]|\[NodeAlphaFeature\]|\[NodeFeature:Eviction\]" --test_args=--feature-gates=DynamicKubeletConfig=true,LocalStorageCapacityIsolation=true --kubelet-flags="--cgroups-per-qos=true --cgroup-root=/" --test-timeout=4h0m0s --image-config-file=/workspace/test-infra/jobs/e2e_node/image-config-serial.yaml: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 137 Passed Tests

Show 932 Skipped Tests