-
Notifications
You must be signed in to change notification settings - Fork 40k
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
node e2e test flake: problems deleting/creating instances #24479
Comments
Build log link doesn't work but you should probably file an internal bug for the 500 (actually if it's "BackendError" but the operation actually succeeded, it's b/27367941) |
Sigh, sorry, the file seems to be gone now since the tests got rerun. Closing since we don't have much to go off of. |
I think I found another instance of this. There really isn't much in the logs to go off of though. |
Happened again: logs
|
This occurred to my PR 4 times in a row this morning. Help needed. @pwittrock @ixdy @k8s-oncall. |
I'm seeing this on all of mine too. |
Probably related to #25639. We keep running out of IP address quota because we're leaking VMs all over the place. |
Now the log only shows "Not Found". For example, see thislog |
node e2e was a mess yesterday, but we should be in the clear now. please reopen if you continue to see failures. |
Reactivating. This appears to be happening again. See log |
Looks like all recent PRs since Jun 13, 2016 5:36 PM PST are hitting this: http://kubekins.dls.corp.google.com:8081/job/node-pull-build-e2e-test/ |
@saad-ali any idea how I build this image? |
Trying this out: per
|
The images are back in the project and I went through and retested all the affected tests |
Thanks @fejta! |
Build log
Was immediately followed by
The text was updated successfully, but these errors were encountered: