This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 5 failed / 694 succeeded
Started2020-01-17 06:05
Elapsed35m27s
Revision
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/499872d1-5a30-4904-8cc9-2ad33447fa6c/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/499872d1-5a30-4904-8cc9-2ad33447fa6c/targets/test
job-versionv1.18.0-alpha.1.848+916edd922e528f
revisionv1.18.0-alpha.1.848+916edd922e528f

Test Failures


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

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\sreplication\scontroller\sacross\szones$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/ubernetes_lite.go:59
Jan 17 06:19:11.863: 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_13.xml

Filter through log files | View test history on testgrid


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

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 17 06:20:57.771: 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_27.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Dynamic PV (default fs)] subPath should support existing directories when readOnly specified in the volumeSource 6m24s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sIn\-tree\sVolumes\s\[Driver\:\saws\]\s\[Testpattern\:\sDynamic\sPV\s\(default\sfs\)\]\ssubPath\sshould\ssupport\sexisting\sdirectories\swhen\sreadOnly\sspecified\sin\sthe\svolumeSource$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/subpath.go:392
Jan 17 06:25:32.831: Unexpected error:
    <*errors.errorString | 0xc0022fc1a0>: {
        s: "expected pod \"pod-subpath-test-dynamicpv-x5nf\" success: Gave up after waiting 5m0s for pod \"pod-subpath-test-dynamicpv-x5nf\" to be \"success or failure\"",
    }
    expected pod "pod-subpath-test-dynamicpv-x5nf" success: Gave up after waiting 5m0s for pod "pod-subpath-test-dynamicpv-x5nf" to be "success or failure"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:829
				
				Click to see stdout/stderrfrom junit_19.xml

Find pod-subpath-test-dynamicpv-x5nf mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-storage] PVC Protection Verify "immediate" deletion of a PVC that is not in active use by a pod 5m10s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-storage\]\sPVC\sProtection\sVerify\s\"immediate\"\sdeletion\sof\sa\sPVC\sthat\sis\snot\sin\sactive\suse\sby\sa\spod$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/pvc_protection.go:65
Jan 17 06:24:59.932: While creating pod that uses the PVC or waiting for the Pod to become Running
Unexpected error:
    <*errors.errorString | 0xc0012c2f00>: {
        s: "pod \"pvc-tester-pdrww\" is not Running: timed out waiting for the condition",
    }
    pod "pvc-tester-pdrww" 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/pvc_protection.go:88
				
				Click to see stdout/stderrfrom junit_06.xml

Find that mentions in log files | View test history on testgrid


Test 25m40s

error during platforms/linux/amd64/ginkgo --nodes=30 platforms/linux/amd64/e2e.test -- --kubeconfig=/tmp/kops457075919/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-1547282733.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 | View test history on testgrid


Show 694 Passed Tests

Show 4158 Skipped Tests