Move test_config.yaml settings into per-app metadata.yaml files
#1161
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change splits up
test_config.yaml, putting its contents into each app'smetadata.yamlfile. This is nice from a tidiness perspective, because there are fewer files to worry about, but it's also nice because now when you adjust the test skips for an app, it doesn't run all tests for all apps, which is what it had to do when there was a centraltest_config.yamlfile. This is extra nice because running all tests for all apps is "heavy" in that it takes longer and is more likely to overload the apache servers, run us out of various quotas, etc.Related issue
offshoot of b/270147175.
How has this been tested?
In addition to automated tests, I ran the tests before and after this change and verified that the PASS/SKIP log messages were identical before and after (after sorting). They were, after fixing some bugs.
Checklist: