This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 3 failed / 696 succeeded
Started2020-01-17 01:00
Elapsed27m51s
Revision
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/2464d45f-4c03-4e4c-a40d-10626fa93b6c/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/2464d45f-4c03-4e4c-a40d-10626fa93b6c/targets/test
job-versionv1.18.0-alpha.1.838+2ea483b17e460c
revisionv1.18.0-alpha.1.838+2ea483b17e460c

Test Failures


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

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 01:12:13.946: Pods were not evenly spread across zones.  1 in one zone and 3 in another zone
Expected
    <int>: 1
to be within 1 of ~
    <int>: 3
/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_22.xml

Filter through log files


Kubernetes e2e suite [sig-storage] In-tree Volumes [Driver: aws] [Testpattern: Inline-volume (ext3)] volumes should allow exec of files on the volume 5m40s

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\:\sInline\-volume\s\(ext3\)\]\svolumes\sshould\sallow\sexec\sof\sfiles\son\sthe\svolume$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/storage/testsuites/volumes.go:193
Jan 17 01:19:39.454: Unexpected error:
    <*errors.errorString | 0xc00265a330>: {
        s: "expected pod \"exec-volume-test-inlinevolume-pnjv\" success: Gave up after waiting 5m0s for pod \"exec-volume-test-inlinevolume-pnjv\" to be \"success or failure\"",
    }
    expected pod "exec-volume-test-inlinevolume-pnjv" success: Gave up after waiting 5m0s for pod "exec-volume-test-inlinevolume-pnjv" 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_29.xml

Find exec-volume-test-inlinevolume-pnjv mentions in log files


Test 18m7s

error during platforms/linux/amd64/ginkgo --nodes=30 platforms/linux/amd64/e2e.test -- --kubeconfig=/tmp/kops622422251/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-1922491622.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 696 Passed Tests

Show 4158 Skipped Tests