| commit | 130da8edf5e3767653c0f51455441692f561c88a | [log] [tgz] |
|---|---|---|
| author | Zhuoyao Zhang <zhuoyao@google.com> | Thu Dec 05 23:16:43 2024 +0000 |
| committer | Zhuoyao Zhang <zhuoyao@google.com> | Fri Dec 06 18:15:38 2024 +0000 |
| tree | 3460b2a6dc9ed9e777232415d70fe5c98f0c016b | |
| parent | afdc92c6457db8b3383df783c8ad631d20ceb455 [diff] |
Update the logic to force cleanup all edit monitor instances. Instead of checking the pidfiles, query all the running process with binary ends with "edit_monitor" and kill all of those processes. This ensures that if there are any unexpected edit monitor instances running (e.g. due to b/382135550), the force cleanup can kill those processes as well. Bug: 382135550 Test: atest daemon_manager_test Change-Id: I299f16b7b913e4ee470b5fe9ef0ffdad8d3c0945
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.