[Harness Separation] A temporary trick to help with migration
Due to some technical issues, we can't push code to
test/suite_harness via a change, it has to be done directly
with "git push". That means there will be a short peroid that
cts/harness and test/suite_harness will both live in the android tree
at the same time.
Modify the Android.mk so that
* mk files under harness/ won't be automatically included.
* cts/Android.mk will selectively include mk files under harness/common
and harness/tools
With this change, we can prevent the tree from being broken during
the short peroid.
Bug: 78461075
Bug: 79201478
Bug: 79695450
Test: make cts -j32 WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY=true
TARGET_PRODUCT=aosp_arm64
Test: cts-tradefed run cts --compatibility:include-filter
CtsGestureTestCases
Test: cts/run_unit_tests.sh
Test: make gts -j32 WITH_DEXPREOPT_BOOT_IMG_AND_SYSTEM_SERVER_ONLY=true
TARGET_PRODUCT=aosp_arm64
Change-Id: I20570440f91c062bf03d0986560ce074f19e279a
2 files changed