Loading
Create a new test_module_config entries for TEST_MAPPING options
As part of adding `test_module_config`: go/test-module-config,
we are migrating options from TEST_MAPPING files to Android.bp files.
Several cls have already been submitted, but this is a larger change to
add the test_module_config entries in bulk to reduce churn on the
Android.bp and TEST_MAPPING files.
This topic covers the two of the repos with the most changes needed
(frameworks/base and cts).
The first cls will simply create the entries in the Android.bp file
This is a noop operation until they get used via TEST_MAPPING files.
The process is:
1) Generate new test_module_configs with reasonable names based on
options in TEST_MAPPING files
2) After 1) gets submitted, match the options from Android.bp back to
TEST_MAPPING files and update those TEST_MAPPING files with the
name from the Andriod.bp.
To simplify a little bit, we are also removing adding
"exclude-annotation" androidx.test.filters.FlakyTest and org.junit.Ignore
from the options set in Android.bp since we recently added Flaky
exclusion to all CI test_mapping runs. And junit always ignore @Ignore,
no reason to ask it to.
Test: ci
Change-Id: I3097093d1677a0a5a30c8f4aed7fc96c22c0e84d
Flag: NONE # test rename only