This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 4 failed / 34 succeeded
Started2022-06-24 16:19
Elapsed4h37m
Revision
Builder650508bd-f3d9-11ec-9e31-9224b4edca5e
control_plane_node_os_imagecos-85-13310-1308-1
infra-commit17f5e9583
job-versionv1.25.0-alpha.1.129+42fec42586c441
kubetest-version
revisionv1.25.0-alpha.1.129+42fec42586c441
worker_node_os_imagecos-85-13310-1308-1

Test Failures


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] Should be able to scale a node group down to 0[Feature:ClusterSizeAutoscalingScaleDown] 20m24s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sShould\sbe\sable\sto\sscale\sa\snode\sgroup\sdown\sto\s0\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
test/e2e/autoscaling/cluster_size_autoscaling.go:876
Jun 24 17:50:45.093: timeout waiting 20m0s for appropriate cluster size
test/e2e/autoscaling/cluster_size_autoscaling.go:867
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining multiple pods one by one as dictated by pdb[Feature:ClusterSizeAutoscalingScaleDown] 6m32s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sbe\sable\sto\sscale\sdown\sby\sdraining\smultiple\spods\sone\sby\sone\sas\sdictated\sby\spdb\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
test/e2e/autoscaling/cluster_size_autoscaling.go:736
Jun 24 19:45:23.751: failed to coerce RC into spawning a pod on node ca-minion-group-1-wdgr within timeout
test/e2e/autoscaling/cluster_size_autoscaling.go:1037
				
				Click to see stdout/stderrfrom junit_01.xml

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


Kubernetes e2e suite [sig-autoscaling] Cluster size autoscaling [Slow] should be able to scale down by draining system pods with pdb[Feature:ClusterSizeAutoscalingScaleDown] 25m0s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-autoscaling\]\sCluster\ssize\sautoscaling\s\[Slow\]\sshould\sbe\sable\sto\sscale\sdown\sby\sdraining\ssystem\spods\swith\spdb\[Feature\:ClusterSizeAutoscalingScaleDown\]$'
test/e2e/autoscaling/cluster_size_autoscaling.go:744
Jun 24 18:13:32.342: timeout waiting 20m0s for appropriate cluster size
test/e2e/autoscaling/cluster_size_autoscaling.go:747
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


kubetest Test 4h21m

error during ./hack/ginkgo-e2e.sh --ginkgo.focus=\[Feature:ClusterSizeAutoscalingScaleUp\]|\[Feature:ClusterSizeAutoscalingScaleDown\] --ginkgo.skip=\[Flaky\] --minStartupPods=8 --report-dir=/workspace/_artifacts --disable-log-dump=true --cluster-ip-range=10.64.0.0/14: exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 34 Passed Tests

Show 7020 Skipped Tests