This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 178 succeeded
Started2020-02-15 22:28
Elapsed3h27m
Revision
Buildergke-prow-default-pool-cf4891d4-5bng
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/f73595f0-84ab-4327-bd79-535030903b58/targets/test'}}
pod64d4a582-5042-11ea-9bea-16a0f55e352c
resultstorehttps://source.cloud.google.com/results/invocations/f73595f0-84ab-4327-bd79-535030903b58/targets/test
infra-commitf5dd3ee0e
job-versionv1.18.0-alpha.5.160+3b22fcc7bdcf5c
master_os_imagecos-77-12371-175-0
node_os_imagecos-77-12371-175-0
pod64d4a582-5042-11ea-9bea-16a0f55e352c
repogithub.com/containerd/cri
repo-commitcf0e0a1e2c864e7115098f7a7624056bc0749df7
repos{u'github.com/containerd/cri': u'master'}
revisionv1.18.0-alpha.5.160+3b22fcc7bdcf5c

Test Failures


Kubernetes e2e suite [sig-autoscaling] DNS horizontal autoscaling [Serial] [Slow] kube-dns-autoscaler should scale kube-dns pods when cluster size changed 5m33s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sDNS\shorizontal\sautoscaling\s\[Serial\]\s\[Slow\]\skube\-dns\-autoscaler\sshould\sscale\skube\-dns\spods\swhen\scluster\ssize\schanged$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/dns_autoscaling.go:105
Feb 16 00:30:28.971: Unexpected error:
    <*errors.errorString | 0xc002918050>: {
        s: "timeout waiting 5m0s for appropriate cluster size",
    }
    timeout waiting 5m0s for appropriate cluster size
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/autoscaling/dns_autoscaling.go:143
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works 1m4s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sSchedulerPreemption\s\[Serial\]\svalidates\sbasic\spreemption\sworks$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:104
Feb 16 01:44:40.198: Unexpected error:
    <*errors.errorString | 0xc00037e200>: {
        s: "pod ran to completion",
    }
    pod ran to completion
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:672
				
				Click to see stdout/stderrfrom junit_01.xml

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


Kubernetes e2e suite [sig-scheduling] SchedulerPreemption [Serial] validates lower priority pod preemption by critical pod 1m2s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-scheduling\]\sSchedulerPreemption\s\[Serial\]\svalidates\slower\spriority\spod\spreemption\sby\scritical\spod$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:184
Test Panicked
/usr/local/go/src/runtime/panic.go:75

Panic: runtime error: index out of range [0] with length 0

Full stack:
k8s.io/kubernetes/test/e2e/scheduling.glob..func5.4()
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/preemption.go:216 +0xa5e
k8s.io/kubernetes/test/e2e.RunE2ETests(0xc0002fc300)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e.go:111 +0x30a
k8s.io/kubernetes/test/e2e.TestE2E(0xc0002fc300)
	_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/e2e_test.go:111 +0x2b
testing.tRunner(0xc0002fc300, 0x4cf9b50)
	/usr/local/go/src/testing/testing.go:909 +0xc9
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:960 +0x350
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Test 3h9m

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Serial\]|\[Disruptive\] --ginkgo.skip=\[Flaky\]|\[Feature:.+\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 178 Passed Tests

Show 4678 Skipped Tests