This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 7 failed / 46 succeeded
Started2019-08-20 09:44
Elapsed4h27m
Revision
Buildergke-prow-ssd-pool-1a225945-c5n1
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/5e8d349a-0590-4bce-9644-3dad59ac74df/targets/test'}}
podf5f1410b-c32e-11e9-be5c-ee22131cc068
resultstorehttps://source.cloud.google.com/results/invocations/5e8d349a-0590-4bce-9644-3dad59ac74df/targets/test
infra-commit3c673e642
job-versionv1.15.4-beta.0.3+7c8601453813e0
podf5f1410b-c32e-11e9-be5c-ee22131cc068
repok8s.io/kubernetes
repo-commit7c8601453813e06a9cecaf7cf0c2a580d1a93499
repos{u'k8s.io/kubernetes': u'release-1.15'}
revisionv1.15.4-beta.0.3+7c8601453813e0

Test Failures


E2eNode Suite [k8s.io] Docker features [Feature:Docker][Legacy:Docker] when live-restore is enabled [Serial] [Slow] [Disruptive] containers should not be disrupted when the daemon shuts down and restarts 5m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sDocker\sfeatures\s\[Feature\:Docker\]\[Legacy\:Docker\]\swhen\slive\-restore\sis\senabled\s\[Serial\]\s\[Slow\]\s\[Disruptive\]\scontainers\sshould\snot\sbe\sdisrupted\swhen\sthe\sdaemon\sshuts\sdown\sand\srestarts$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/docker_test.go:41
Unexpected error:
    <*errors.errorString | 0xc0002164c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:113
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [k8s.io] Downward API [Serial] [Disruptive] [NodeFeature:EphemeralStorage] Downward API tests for local ephemeral storage should provide default limits.ephemeral-storage from node allocatable 5m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sDownward\sAPI\s\[Serial\]\s\[Disruptive\]\s\[NodeFeature\:EphemeralStorage\]\sDownward\sAPI\stests\sfor\slocal\sephemeral\sstorage\sshould\sprovide\sdefault\slimits\.ephemeral\-storage\sfrom\snode\sallocatable$'
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/common/downward_api.go:271
Unexpected error:
    <*errors.errorString | 0xc0010a1fb0>: {
        s: "expected pod \"downward-api-e3db3132-1b52-48a2-88b9-3812339d2570\" success: Gave up after waiting 5m0s for pod \"downward-api-e3db3132-1b52-48a2-88b9-3812339d2570\" to be \"success or failure\"",
    }
    expected pod "downward-api-e3db3132-1b52-48a2-88b9-3812339d2570" success: Gave up after waiting 5m0s for pod "downward-api-e3db3132-1b52-48a2-88b9-3812339d2570" to be "success or failure"
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2342
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Find downward-api-e3db3132-1b52-48a2-88b9-3812339d2570 mentions in log files | View test history on testgrid


E2eNode Suite [k8s.io] GarbageCollect [Serial][NodeFeature:GarbageCollect] Garbage Collection Test: Many Restarting Containers Should eventually garbage collect containers when we exceed the number of dead containers per container 15m8s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sGarbageCollect\s\[Serial\]\[NodeFeature\:GarbageCollect\]\sGarbage\sCollection\sTest\:\sMany\sRestarting\sContainers\sShould\seventually\sgarbage\scollect\scontainers\swhen\swe\sexceed\sthe\snumber\sof\sdead\scontainers\sper\scontainer$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/garbage_collector_test.go:170
Unexpected error:
    <*errors.errorString | 0xc0002164c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:113
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Filter through log files | View test history on testgrid


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

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[k8s\.io\]\sLocalStorageEviction\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:455
Unexpected error:
    <*errors.errorString | 0xc0002164c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:113
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Filter through log files | View test history on testgrid


E2eNode Suite [sig-node] HugePages [Serial] [Feature:HugePages][NodeFeature:HugePages] With config updated with hugepages feature enabled should assign hugepages as expected based on the Pod spec 5m27s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sHugePages\s\[Serial\]\s\[Feature\:HugePages\]\[NodeFeature\:HugePages\]\sWith\sconfig\supdated\swith\shugepages\sfeature\senabled\sshould\sassign\shugepages\sas\sexpected\sbased\son\sthe\sPod\sspec$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/hugepages_test.go:163
Unexpected error:
    <*errors.errorString | 0xc0003d6980>: {
        s: "Gave up after waiting 5m0s for pod \"pod88d82a03-f603-4dfa-a2c5-77392f36ee67\" to be \"success or failure\"",
    }
    Gave up after waiting 5m0s for pod "pod88d82a03-f603-4dfa-a2c5-77392f36ee67" to be "success or failure"
occurred
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/hugepages_test.go:191
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Find pod88d82a03-f603-4dfa-a2c5-77392f36ee67 mentions in log files | View test history on testgrid


E2eNode Suite [sig-node] Resource-usage [Serial] [Slow] regular resource usage tracking resource tracking for 10 pods per node 5m22s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=E2eNode\sSuite\s\[sig\-node\]\sResource\-usage\s\[Serial\]\s\[Slow\]\sregular\sresource\susage\stracking\sresource\stracking\sfor\s10\spods\sper\snode$'
_output/local/go/src/k8s.io/kubernetes/test/e2e_node/resource_usage_test.go:49
Unexpected error:
    <*errors.errorString | 0xc0002164c0>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/local/go/src/k8s.io/kubernetes/test/e2e/framework/pods.go:113
				
				Click to see stdout/stderrfrom junit_ubuntu-gke-1804-d1703-0-v20190813a_01.xml

Filter through log files | View test history on testgrid


Node Tests 4h25m

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-d1703-0-v20190813a --image-project=ubuntu-os-gke-cloud-devel: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 46 Passed Tests

Show 264 Skipped Tests