test-infra: Excessive failed batches

Deck is showing lots of recent consecutive batch job failures. It looks like the last batch and the current batch are healthier now, but deck currently shows 15 (nearly) consecutive batch failures. /cc @ixdy http://prow.k8s.io/?repo=kubernetes%2Fkubernetes&type=batch

This error text is common between the failures that I checked:

cmd/kube-proxy/app/server.go:402:19: cannot use config.Burst (type int32) as type int in assignment

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 15 (14 by maintainers)

Most upvoted comments

Or /lgtm cancel since the breaking changes will most likely not be merged at the point you start the tests, thus /test all ends up green and the PR is added back to a batch.

0xmichalis on Nov 17, 2017

The two PRs didn’t have non-logic conflict so needs-rebase wasn’t detected. It’d be good to have a way to find which PR is the criminal of the batch testing failure and exclude it out of the batch or even the submit-queue.

xiangpengzhao on Nov 15, 2017

That’s because https://github.com/kubernetes/kubernetes/pull/53850 changed the type and was merged just a day ago.

-	Burst int
 +	Burst int32

https://github.com/kubernetes/kubernetes/commit/7950609b31df2354f31199dba6706d62959b48b4#diff-96a1b32fdd44ac3b9ab11bfaa36df4cdR40

Then https://github.com/kubernetes/kubernetes/pull/53787 will not be needed any longer. I will close it.

xiangpengzhao on Nov 15, 2017