-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
playground: error rates increasing #18322
Comments
My experience from Denver, COI have never noticed an issue before.. but I could repeatably create the issue from the go playground link |
Same thing from San Francisco running @kris-nova's program in #18322 (comment), |
The old infrastructure ("vm:true", aka Managed VMs) appears to be flaky, and we (me, and the App Engine team) can't figure out why. It's up and running on the new infrastructure ("env:flex", aka "Flexible Beta 2") now, so should be more stable. If you see any errors at all, re-open this issue. Relevant CLs: |
I'm sorry for not using the template or having concrete details, but it's hard to link to a failed invocation of the playground.
Over the last few months I've experienced an increase in failures running playground samples, "error communicating with backend server".
I've experienced this from multiple geographies including Australia, Japan, Korea, Amsterdam, London, and Paris, and others have reported similar results (again anocdotally, I do not have a count of the exact number of reports) so I believe it is not localised to my computers or location.
Obviously once then compile succeeds the result is cached and the problem masked.
Have the error rates monitored from the playground been increasing? Can something be done to reverse this trend?
The text was updated successfully, but these errors were encountered: