-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RBE bazel jobs are timing out #20628
Comments
CC @fejta |
Lots of CI uses bazel, and bazel almost always uses RBE. |
Not using RBE in #20626 can make |
running into this in #20630 |
This appears to block all merges into this repo, last merge was 9 hours ego and there is a bunch of merge-eligible PRs stuck in retesting: https://github.com/kubernetes/test-infra/pulls?q=is%3Apr+is%3Aopen+label%3Aapproved+label%3Algtm+-label%3A%22do-not-merge%2Fhold%22 |
FYI @kubernetes/release-engineering |
Current hypothesis is different bazel versions in k8s/test-infra and k8s/kubernetes caused confusion to RBE, and #20632 is an attempt to fix |
Seeing tests reliably going through now: |
The root cause of this problem was still not very clear, but according to RBE team it's possible that one of their dependencies had a bad release which was mitigated yesterday. Checked again and all affected tests are passing now, so closing this bug. /close |
@chaodaiG: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What happened:
There are several prow jobs started failing timing out after 2 hours, inspecting the logs and they were hanging at bazel test phase.
https://testgrid.k8s.io/sig-release-master-blocking#bazel-build-master
https://prow.k8s.io/?repo=kubernetes%2Ftest-infra&job=pull-test-infra-integration
https://prow.k8s.io/?repo=kubernetes%2Ftest-infra&job=pull-test-infra-bazel
One noticeable common factor among them is the usage of RBE
The text was updated successfully, but these errors were encountered: