Added check for blink's perf cfg file. The bisect/perf bots work by modifying a ...
commitb3c0ee731210b12a18adc0362212341218462b83
authorsimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 22 Oct 2013 21:58:38 +0000 (22 21:58 +0000)
committersimonhatch@chromium.org <simonhatch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 22 Oct 2013 21:58:38 +0000 (22 21:58 +0000)
treed895ef242f04f3aca03ce26ab32ed33fbda82ba6
parent6fcf47f96fb0f62723a0cd2f8b0dcab3aa9a5160
Added check for blink's perf cfg file. The bisect/perf bots work by modifying a .cfg file with the parameters of the job (ie. revision, command, repetitions, etc...) and submitting that as a patch to the bot. Since a single patch can't span both blink and chromium, we need a run-perf-test.cfg in each depot that we're likely to try running perf tests from.

Waiting on: https://codereview.chromium.org/33553003/

BUG=
NOTRY=true

Review URL: https://codereview.chromium.org/34723005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@230222 0039d316-1c4b-4281-b951-d872f2087c98
tools/run-bisect-perf-regression.py