[autotest] Perf tests must speicify config data.
Perviously, the specification of config data is not enforced
by code. When missing, default config data will be used. This
causes inconsistency when people lands their test first and the
change to perf_dashboard_config is pushed to prod later.
This cl fixes this problem by enforcing the specification
of config data for all perf tests. If the config data is
missing, perf data will not be uploaded.
BUG=chromium:371022
TEST=Test locally by removing entry of power_Resume from
perf_dashboard_config. Confirmed data will not be uploaded.
unittests.
Change-Id: Icaa1e854c33a617218d87b6c496894a8cf178382
Reviewed-on: https://chromium-review.googlesource.com/198747
Tested-by: Fang Deng <fdeng@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Commit-Queue: Fang Deng <fdeng@chromium.org>
2 files changed