-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/build: vcs-test.golang.org is down #27127
Comments
Change https://golang.org/cl/130418 mentions this issue: |
Change https://golang.org/cl/130475 mentions this issue: |
The SNI challenge is not supported by Let's Encrypt anymore, replaced by the ALPN one, which requires an extra config entry. Also, autocert now knows how to do RSA fallback, so remove that code. Updates golang/go#27127 Change-Id: I45f907101a7c7a57d1a8376208dba4afb10ed6fd Reviewed-on: https://go-review.googlesource.com/130418 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Quoting https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances under "Best Practices": > Grant the instance the https://www.googleapis.com/auth/cloud-platform > scope to allow full access to all Google Cloud APIs, so that the IAM > permissions of the instance are completely determined by the IAM roles > of the service account. Updates golang/go#27127 Change-Id: Icceb3b17a12223199efd67d27f6bca2b71f8fadc Reviewed-on: https://go-review.googlesource.com/130475 Reviewed-by: Andrew Bonventre <andybons@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
I am trying to run some git module tests right now and it appears to be down for me.
|
We are aware of the issue still and apologize. There are some unforeseen internal issues that are still being worked out. |
@andybons Thanks for the update. I don't have a lot of context on why these tests use |
vcs-test.golang.org is back up. |
@jasonkeene I don’t know the history of vcs-test, so I’m unable to answer your question. Perhaps file a new issue specific to your question? |
We are aware of the issue and are working on it.
The text was updated successfully, but these errors were encountered: