-
Notifications
You must be signed in to change notification settings - Fork 38.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
Failure cluster [6d268a...] failed 49 builds, 3 jobs, and 1 tests over 1 days #45998
Comments
@fejta - trying to triage issues; tough to route to a sig with info included here. any suggestions? |
And if you open that link: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-gke-stackdriver/3608 Pretty clear that this has to do with |
Also if you search for and then look at the history: So my guess is maybe: |
@fejta Thanks! I'll take a look on Monday Btw, what is the status with the |
Thanks much! We haven't been forcing it to stay up to date because it causes to many merge conflicts, we're working on the replacement (see test_owners.json) |
@fejta Cool, nice to hear! I actually liked when issues were auto-assigned to me back in the days |
But meanwhile I'll make logging tests less restrictive |
…rictive Automatic merge from submit-queue Make Stackdriver Logging e2e tests less restrictive To reduce flakiness, as described in #45998, until further investigation /cc @fgrzadkowski
@fejta I fixed tests for gce. The only missing piece for gke is whitelisting the project on SD side. |
Failure cluster 6d268a83c25eb70f6b68
Error text:
Failure cluster statistics:
1 tests failed, 3 jobs failed, 49 builds failed.
Failure stats cover 1 day time range '15 May 2017 22:03 UTC' to '16 May 2017 22:03 UTC'.
Top failed tests by jobs failed:
Top failed jobs by builds failed:
Current Status
The text was updated successfully, but these errors were encountered: