| commit | b5aa16d44f38fee6f93e05fd41e7c798b7bc0d34 | [log] [tgz] |
|---|---|---|
| author | Jaewoong Jung <jungjw@google.com> | Fri Mar 13 15:51:54 2020 -0700 |
| committer | Jaewoong Jung <jungjw@google.com> | Thu Mar 19 06:47:35 2020 -0700 |
| tree | f3c0e85206f174afe7375ed8f6b6011b327f83ab | |
| parent | 352e6a4d183759315de61db6a96c110f5e1d4381 [diff] |
Fix test suite data files issue. The current test suite rule implementation has a bug where test data files are excluded from the final suite zip files when a suite doesn't have a designated testcases output directory, which is represented by COMPATIBILITY_TESTCASES_OUT_$(suite_name). Specifically, the rule that collects test data files for each suite filters out suite output paths that conflict with module output paths, which happens when a suite doesn't have its own testcases output directory. It seems to have been done this way just to avoid make rule conflict errors, but it ended up causing missing test data files. This change fixes it by adding an indexing purpose only test suit file variable. Fixes: 140761783 Test: m general-tests Test: Compared before vs after, no meaningful differences. Test: Changed bc-tests to a device test and built general-tests. Test: Before - data files missing, after - data files present Change-Id: I2008992f4144c6ee115f4b4e4ac9caa4312bbe34
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.