Add tool/perf/measurements path to check for CQ jobs.

Add tool/perf/measurements path to check for CQ jobs.

BUG=462581
Committed: https://crrev.com/99e1ac1d217174dad7a862f6a0fc44950d503737
Cr-Commit-Position: refs/heads/master@{#325296}

[prasadv, 2015-04-15 19:55:21]

prasadv@chromium.org changed reviewers:
+ qyearsley@chromium.org

[qyearsley, 2015-04-15 19:56:18]

On 2015/04/15 19:55:21, prasadv wrote:

LGTM

[prasadv, 2015-04-15 20:04:18]

The CQ bit was checked by prasadv@chromium.org

[commit-bot: I haz the power, 2015-04-15 20:06:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1061803004/1

[commit-bot: I haz the power, 2015-04-15 20:46:21]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-04-15 20:47:12]

Patchset 1 (id:??) landed as
https://crrev.com/99e1ac1d217174dad7a862f6a0fc44950d503737
Cr-Commit-Position: refs/heads/master@{#325296}

[nednguyen, 2015-04-27 22:02:53]

nednguyen@google.com changed reviewers:
+ nednguyen@google.com

[nednguyen, 2015-04-27 22:02:54]

https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
File tools/run-bisect-perf-regression.py (right):

https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
tools/run-bisect-perf-regression.py:640: benchmark =
os.path.basename(os.path.splitext(affected_file)[0])
This seems to make the assumption that benchmark's name is the same as
measurement name? Note that this may not always be True.

[prasadv, 2015-04-27 22:14:50]

https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
File tools/run-bisect-perf-regression.py (right):

https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
tools/run-bisect-perf-regression.py:640: benchmark =
os.path.basename(os.path.splitext(affected_file)[0])
On 2015/04/27 22:02:54, nednguyen wrote:
> This seems to make the assumption that benchmark's name is the same as
> measurement name? Note that this may not always be True.

Is there any way to find measurement to benchmark mapping?

[nednguyen, 2015-04-27 22:23:09]

On 2015/04/27 22:14:50, prasadv wrote:
>
https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
> File tools/run-bisect-perf-regression.py (right):
> 
>
https://codereview.chromium.org/1061803004/diff/1/tools/run-bisect-perf-regre...
> tools/run-bisect-perf-regression.py:640: benchmark =
> os.path.basename(os.path.splitext(affected_file)[0])
> On 2015/04/27 22:02:54, nednguyen wrote:
> > This seems to make the assumption that benchmark's name is the same as
> > measurement name? Note that this may not always be True.
> 
> Is there any way to find measurement to benchmark mapping?

You can iterate through all benchmark files in benchmark/ folder, then for each
benchmark file, find the list all imported modules in that file that match the
module of the changed measurement files. If the list is non empty, then the
benchmark is "modified".