-
Notifications
You must be signed in to change notification settings - Fork 39.6k
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
Flake? E2E Test failed with GCP quota exceeded #48688
Comments
@fasaxc There are no sig labels on this issue. Please add a sig label by: |
@kubernetes/sig-testing-misc |
@fasaxc: Reiterating the mentions to trigger a notification: 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. |
/assign @krzyzacy |
@krzyzacy IIUC, your new tool, boskos, is destined for fixing these kinds of failures, right? |
no, that should be janitor, and seems something is leaking badly from the test |
I'll check the project, @MrHohn IMO it does not even run test, any suspicious? |
Quick update: Seems like the auto-network includes more regions than before so we hit quota limit when too many PR jobs are running together. |
sent a quota bump, will need a better design in the future. |
/close |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
CI tests for #48469 failed with a quota error:
Full logs:
https://storage.googleapis.com/kubernetes-jenkins/pr-logs/pull/48469/pull-kubernetes-kubemark-e2e-gce/38580/build-log.txt
What you expected to happen:
Clean test run.
How to reproduce it (as minimally and precisely as possible):
I don't know wnough about the test infrastructure to know.
Anything else we need to know?:
Environment:
kubectl version
): Unknown (test infra)uname -a
):The text was updated successfully, but these errors were encountered: