The regularly running perf-AV tests require re-baseline-ing of expectations about once a week. The steps involved in re-baseline-ing are:

Identify the tests to update, based off reported results.
Figure out reva and revb values, which is the start and end revision numbers for the range that we should use to obtain new thresholds.
Modify lines in perf_expectations.json that relate to the tests to be updated, so that they may be used as input to make_expectations.py.

This CL tracks creating a python script to do the last step listed above.

BUG=172930

Review URL: https://chromiumcodereview.appspot.com/12101002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@189395 0039d316-1c4b-4281-b951-d872f2087c98
4 files changed