How to Build Android 10 with Build Acceleration 11.3 ?

Question

I followed the installation guide to set up 2 agent hosts (each has 10 agents running) and install Cluster Manager and eMake on my laptop. Tried the sample moxie project to make sure distributed build can work.

Then I referenced to this document to try to accelerate AOSP (Android 10) build

https://docs.cloudbees.com/docs/cloudbees-build-acceleration/11.3/emake-user-guide/android-performance

but failed not too long after issuing emake command, don't know the exact failure reason.

issued command: emake --emake-cm=localhost --emake-android-version=10.0.0

failure message: please see the captured running log at the end of this article.

thanks for any help.

Answer 1

Answer by eric melski · Dec 15, 2020 at 10:51 PM

The two CPU's indicated by your output are both pretty old. The emake host is running on an Intel Core i7-4510U, which was first released in 2014, while the agent host claims to be an Intel Xeon CPU E5-2630 v3, also released in 2014. Nevertheless as far as I can tell both should be capable of running the `eckati` executable. Perhaps the VM is misrepresenting its capabilities? I'll log a ticket internally to rebuild `eckati` to target an older architecture to be safe, but that probably won't get released until early 2021 at this point. In the meantime, you may be able to work around this by copying the `ckati` executable that comes with AOSP itself over the `eckati` found at `/opt/ecloud/i686_Linux/conf/types/android/10.0.0/eckati` in your installation -- you'll need to do that on on both the agent and emake hosts. One last word of caution: based on this info I think your system may not be powerful enough to build AOSP in a practical amount of time, as it is very memory and CPU intensive. I think 8 cores and 64GB RAM is just about the smallest system I would personally use to build AOSP. In my lab I usually use 64 cores and 256GB RAM, and even with that an uncached build takes more than half an hour to complete. I imagine on a 4-core laptop like you've described the build will be intolerably long.

0 Show 5 · Share

jinkailau · Dec 16, 2020 at 12:27 AM 0

Share

Thanks for your help and advice, I will try it out today and report the result.

jinkailau · Dec 16, 2020 at 02:43 AM 0

Share

@eric melski
The following error was encountered:

ERROR EC1073: Job caused multiple agents to fail.
ERROR EC1073: For more information see https://docs.cloudbees.com/cba/EC1073
make: *** [run_soong_ui] Error 1
Finished build: 3 Duration: 43:02 (m:s) Cluster availability: 99%

All I need to do is to rerun emake with "--keep-going" option appended as described in the suggested documentation, right?

eric melski ♦♦ · Dec 16, 2020 at 03:19 AM 0

Share

No, this error indicates that running the build actually caused several agents to go offline. I suspect that this is a consequence of trying to run this build on a system that is not adequate to the task. You may find some clues in the system log on the agent host, or in the agent logs on the agent host, but I think fundamentally you probably just need a more powerful system to run this build.

jinkailau · Dec 16, 2020 at 04:08 AM 0

Share

@eric melski I am assigned only two virtual machines, each has 10 cores and 30GB RAM, to do the experiment. These two VMs are to serve as the agent hosts and I use my laptop to run emake (and Cluster Manager is also running on this laptop) to build Android. According to your suggestion, I ran ecconfig to reconfigure these two VMs to provide 6 agents per host. Hope this change can make the whole build process smoothly completed.

jinkailau · Dec 17, 2020 at 05:53 AM 0

Share

@eric melski I can build the AOSP now, but when I try to use Build Acceleration to build our private Android product code, I encountered following error: failed to initialize build cache at /home/MYACCOUNT/.cache/go-build: mkdir /home/MYACCOUNT/.cache: permission denied. Should I export GOCACHE environment variable to point to somewhere else (eg. /tmp/go-cache) before I issuing the emake? Thanks.

Answer 2

emake seems can't handle dependencies well for those modules from SoC vendor, failed with following message: --- HIDL java: system/libhidl/transport/manager/1.0/IServiceManager.hal system/libhidl/transport/manager/1.0/IServiceNotification.hal system/libhidl/transport/current.txt => srcs.srcjar //system/libhidl/transport/manager/1.0:android.hidl.manager-V1.0-java turbine [common] //system/libhidl/transport/manager/1.0:android.hidl.manager-V1.0-java for turbine [common] //device/symbol/valueadds/diagdaemon:dd_service-raw for prebuilts [common] //device/symbol/valueadds/diagdaemon:dd_service for turbine [common] //device/symbol/valueadds/diagdaemon:CollectorFramework-raw for prebuilts [common] //device/symbol/valueadds/diagdaemon:CollectorFramework for turbine [common] //frameworks/base/services/core:services.core.unboosted for javac [common] module services.core.unboosted missing dependencies: vendor.qti.hardware.servicetracker-V1.0-java FAILED: echo "module services.core.unboosted missing dependencies: vendor.qti.hardware.servicetracker-V1.0-java" && false ninja: build stopped: subcommand failed. make: *** [run_soong_ui] Error 1 --- This entire code base of our private Android product can be successfully built using normal Android build process.

How to Build Android 10 with Build Acceleration 11.3 ?

2 Replies

Your answer

Follow this Question

Related Questions