This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 695 succeeded
Started2020-01-16 06:43
Elapsed32m20s
Revision
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/d98ccb30-939a-4b50-9aac-75da6541d199/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/d98ccb30-939a-4b50-9aac-75da6541d199/targets/test
job-versionv1.18.0-alpha.1.810+f437ff75d45517
revisionv1.18.0-alpha.1.810+f437ff75d45517

Test Failures


Kubernetes e2e suite [sig-scheduling] Multi-AZ Clusters should spread the pods of a service across zones 4.70s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sMulti\-AZ\sClusters\sshould\sspread\sthe\spods\sof\sa\sservice\sacross\szones$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/ubernetes_lite.go:55
Jan 16 07:00:42.217: Pods were not evenly spread across zones.  0 in one zone and 4 in another zone
Expected
    <int>: 0
to be within 1 of ~
    <int>: 4
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/ubernetes_lite.go:173
				
				Click to see stdout/stderrfrom junit_28.xml

Filter through log files


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir] One pod requesting one prebound PVC should be able to mount volume and read from pod1 3m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\]\sOne\spod\srequesting\sone\sprebound\sPVC\sshould\sbe\sable\sto\smount\svolume\sand\sread\sfrom\spod1$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:210
Jan 16 06:59:20.287: Unexpected error:
    <*errors.errorString | 0xc0032ee7e0>: {
        s: "pod \"security-context-39fb00a8-7968-4a1d-a1a6-3655696df0d7\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-39fb00a8-7968-4a1d-a1a6-3655696df0d7" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:213
				
				Click to see stdout/stderrfrom junit_21.xml

Find security-context-39fb00a8-7968-4a1d-a1a6-3655696df0d7 mentions in log files


Kubernetes e2e suite [sig-storage] PersistentVolumes-local [Volume type: dir] Two pods mounting a local volume at the same time should be able to write from pod1 and read from pod2 2m34s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPersistentVolumes\-local\s\s\[Volume\stype\:\sdir\]\sTwo\spods\smounting\sa\slocal\svolume\sat\sthe\ssame\stime\sshould\sbe\sable\sto\swrite\sfrom\spod1\sand\sread\sfrom\spod2$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:244
Jan 16 06:59:04.016: Unexpected error:
    <*errors.errorString | 0xc002e6fda0>: {
        s: "pod \"security-context-e2e03647-c209-4b21-8632-6f12c0abd18d\" is not Running: timed out waiting for the condition",
    }
    pod "security-context-e2e03647-c209-4b21-8632-6f12c0abd18d" is not Running: timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/persistent_volumes-local.go:712
				
				Click to see stdout/stderrfrom junit_08.xml

Find security-context-e2e03647-c209-4b21-8632-6f12c0abd18d mentions in log files


Test 22m31s

error during platforms/linux/amd64/ginkgo --nodes=30 platforms/linux/amd64/e2e.test -- --kubeconfig=/tmp/kops953586698/kubeconfig --ginkgo.flakeAttempts=1 --provider=aws --gce-zone=us-west-2a --gce-region=us-west-2 --gce-multizone=false --host=https://api-e2e-kops-aws-ha-uswes-l3e4kr-2114320753.us-west-2.elb.amazonaws.com --cluster-tag=e2e-kops-aws-ha-uswest2.k8s.local --repo-root=. --num-nodes=0 --ginkgo.skip=\[Slow\]|\[Serial\]|\[Disruptive\]|\[Flaky\]|\[Feature:.+\]|\[HPA\]|Dashboard|Services.*functioning.*NodePort --report-dir=/logs/artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files


Show 695 Passed Tests

Show 4158 Skipped Tests