Edit monitor do not monitor the build out directory

We want to monitor the edits under source tree, while the build out
directory is only used to store build outputs. During the build time,
there will be a lot of file changes under the out directory, although
the edit monitor will not send any of the file changes under the out
dir to clearcut, it needs to dispatch all the file change events
which consumes the CUP usage.

This cl will skip the build out directory when scheduling the watchdog
observer in edit monitor.

Test: atest edit_monitor_test
Bug: 381095876
Change-Id: I6759d5f7c7fd37c153bcb1fff29bd8fc37581774
3 files changed
tree: a72c294462a736b3c825948bf0c2d877a6c51899
  1. backported_fixes/
  2. ci/
  3. common/
  4. core/
  5. packaging/
  6. target/
  7. teams/
  8. tests/
  9. tools/
  10. .gitignore
  11. Android.bp
  12. banchanHelp.sh
  13. buildspec.mk.default
  14. Changes.md
  15. CleanSpec.mk
  16. Deprecation.md
  17. envsetup.sh
  18. help.sh
  19. navbar.md
  20. OWNERS
  21. PREUPLOAD.cfg
  22. rbesetup.sh
  23. README.md
  24. shell_utils.sh
  25. tapasHelp.sh
  26. Usage.txt
README.md

Android Make Build System

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.