| commit | 6c171a69b2b826c73006fe75489ee689d6f54161 | [log] [tgz] |
|---|---|---|
| author | Akilesh Kailash <akailash@google.com> | Mon Feb 28 06:29:50 2022 +0000 |
| committer | Akilesh Kailash <akailash@google.com> | Mon Feb 28 06:29:50 2022 +0000 |
| tree | bd40268d50a3c65b236236fa9a3d8ec43f4da899 | |
| parent | afe0e76c28aa389a1ce5fd3f3ab113fc44431482 [diff] |
Enable Async merge during OTA If the async merge has a temporary failure, gracefully fallback to synchronous I/O without failing the OTA merge. Bug: 220991038 Test: 1: OTA on CF pre-submit runs 2: OTA on O6, R4 and Bramble with the following flow on TP builds: BUILD-1 (without-this-patch) -> BUILD-2 (with this patch) -> BUILD-3 (with this patch) Verified the failure path of async merge on all three devices Signed-off-by: Akilesh Kailash <akailash@google.com> Change-Id: I0b499d2cc81f44c74f85745f9165b81d0ce34eba
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.