-
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
build: android builds stuck in waiting_for_machine #48969
Comments
Fallout from https://golang.org/cl/354757. cc @toothrot
https://cloud.google.com/compute/docs/general-purpose-machines#e2_machine_types says: "E2 VMs do not support GPUs, local SSDs, sole-tenant nodes, or nested virtualization." Rolling back for now. |
N2 should support nested virtualization, which we need on the android builders for hardware acceleration. The error @heschi posted is also a problem for a different builder, |
ok, I am confused. sorry. It looks like we set that when we ask for nested virtualization, and possibly also Intel Haswell. |
Change https://golang.org/cl/356071 mentions this issue: |
e2 and n2d instances do not support specifying a MinCPUVersion or NestedVirt. For golang/go#48969 Change-Id: I0c4b359b29cd24302b869748014f848a9b7b5e39 Reviewed-on: https://go-review.googlesource.com/c/build/+/356071 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org>
Change https://golang.org/cl/356629 mentions this issue: |
The n2 machine types that we now use for instances are either Ice Lake or Cascade Lake. The error message we received when creating a VM was specifically to use Cascade Lake, not the older Haswell. For golang/go#48969 Change-Id: I1c05679c2b512ca3bb7dbb0d2efa6f587305f6aa Reviewed-on: https://go-review.googlesource.com/c/build/+/356629 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> Reviewed-by: Carlos Amedee <carlos@golang.org> TryBot-Result: Go Bot <gobot@golang.org>
Change https://golang.org/cl/356630 mentions this issue: |
Also, specify a valid CPU Platform for n2 VMs for OpenBSD. See: https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform#availablezones For golang/go#48969 Change-Id: Id503227ad0fbb844e9eaa923b8b3ac7da591ee76 Reviewed-on: https://go-review.googlesource.com/c/build/+/356630 Trust: Alexander Rakoczy <alex@golang.org> Run-TryBot: Alexander Rakoczy <alex@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
This should be resolved now, along with some quota increases. |
It looks like both android builders are stuck [EDIT: the two emulators for x/tools: amd64-emu and 386-emu]. Not seeing any recent builds at https://build.golang.org. Example:
CC @golang/release
The text was updated successfully, but these errors were encountered: