-
Notifications
You must be signed in to change notification settings - Fork 18k
x/playground: deploy may take over 10 minute and timeout #28046
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
Comments
I wonder if this build command includes building the docker container? I have noticed that building playground docker container became very slow. Specifically fetching packages is slow. Since I was not sure if it was my network, I did not create ticket for that. |
Yes, it does. That's the part that takes up to 8-9 minutes.
I didn't notice that to be the slow part, but thanks for pointing out. I'll watch it more closely next time. |
A data point from today's deploy (for #25462): the cloud build step took 10 min 58 sec. (It was within my 15 minute timeout.) |
Another data point from today's deploy: the cloud build step took 10 min 43 sec. Edit: Another data point from a deploy on 2018-10-26: 10 min 40 sec. |
Two data points for the cloud build step from today's deploy (in #30397), using Go version 1.12:
By now, it's clear we are reliably beyond the 10 minute mark. |
Change https://golang.org/cl/164577 mentions this issue: |
Is it possible it is a problem of app engine? https://groups.google.com/forum/#!topic/google-appengine-go/fBdzFHZ1D5U |
This issue was related to the time it takes to build the Docker image using Cloud Build, which grew from 8~ minutes to 12~ minutes over time, and how it intersected with the default timeout of 10 minutes. The linked thread doesn't seem to be directly related. |
I've ran into this when deploying the Go Playground with Go 1.11.1 recently (see CL 140097), where the cloud build failed because it took more than the default 10 minute timeout:
ERROR: (gcloud.app.deploy) Cloud build failed. Check logs at https://console.cloud.google.com Failure status: UNKNOWN: Error Response: [4] DEADLINE_EXCEEDED
In the recent past, some builds have taken around 9~ minutes. They were faster earlier on.
People have run into the 10 minute timeout in other contexts too. E.g., see https://stackoverflow.com/questions/50046545/google-app-engine-build-timed-out-during-deployment.
For now, this issue is to gather data and see if this keeps happening. We can then decide on how to best deal with it. If you run into this, please post data here. /cc @bradfitz @andybons
Workaround
The easiest temporary workaround I'm currently aware of is to increase the timeout before the
gcloud app deploy
step. For example:Note that it's a global config value.
The text was updated successfully, but these errors were encountered: