Failing job ci-kubetest2-push-binaries

kubernetes / test-infra

Test infrastructure for the Kubernetes project.

Apache License 2.0

3.85k stars 2.66k forks source link

Failing job ci-kubetest2-push-binaries #33803

Open elieser1101 opened 1 week ago

elieser1101 commented 1 week ago

What happened: The ci-kubetest2-push-binaries job is failing

What you expected to happen: Job to succeed

How to reproduce it (as minimally and precisely as possible): Its a periodic job

Please provide links to example occurrences, if any: https://testgrid.k8s.io/sig-testing-kubetest2#ci-kubetest2-push-binaries

k8s-ci-robot commented 1 week ago

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

/sig <group-name>
/wg <group-name>
/committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

BenTheElder commented 1 week ago

This is not a great place to file this sort of issue, it would be better to file it against the kubetest2 repo where the maintainers for that repo are watching

aojea commented 1 week ago

it seems the jobs times out in cloudbuild

Your build timed out. Use the [--timeout=DURATION] flag to change the timeout threshold.

aojea commented 1 week ago

The cloudbuild seems to be here https://github.com/kubernetes-sigs/kubetest2/blob/master/hack/ci/push-binaries/cloudbuild.yaml

does it take more than 1 hour to build the binaries? @upodroid is a cloudbuild machine problem or a timeout problem?