-
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: tracking bug for Android armv7 builders #9579
Comments
Unfortunately we can't run KVM on GCE. They've disabled nested KVM it seems. |
I know the team that's working on nested-KVM on GCE, and in contact. It's likely that I can share more details soon. |
Btw, this is already rolled out to the GCE, not an upcoming project or anything. I was able to run the Android emulator on a bare ubuntu instance earlier today and the tests are passing. They are 30x slower as usual. |
I doubt it's using KVM, then. I tried to use qemu with KVM the other day for Plan 9 and it didn't work. I had to use my home Linux server instead. |
With android/amd64 and android/386 running I don't think we need this. There are device builders that test on real devices for arm and arm64. |
I'm working on the android-armv7 builder according to the plan explained on https://golang.org/s/builderplan.
The plan is to depend on one of the official armv7 Android emulator images -- Android emulator is based on qemu-kvm and does arm emulation.
I've drafted the initial work on https://go-review.googlesource.com/#/c/2730/.
The text was updated successfully, but these errors were encountered: