Move bisect-perf-regression.py into auto_bisect directory.

Move bisect-perf-regression.py into auto_bisect directory.

The purpose of this is to continue gathering all the related code together, and to make it easier to run pylint/tests for the main module which still contains most of the code.

After doing this, pylint and the tests caught a couple of things -- one unused variable name, and after the script changed directory, some of the paths had to be modified as well.

BUG=

Committed: https://crrev.com/62edbcf1e8e5dd1386693b7b4b90169e72bd7300
Cr-Commit-Position: refs/heads/master@{#296847}

[qyearsley, 2014-09-11 16:36:27]

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

[qyearsley, 2014-09-11 16:38:38]

https://codereview.chromium.org/564663002/diff/20001/tools/auto_bisect/bisect...
File tools/auto_bisect/bisect.cfg (right):

https://codereview.chromium.org/564663002/diff/20001/tools/auto_bisect/bisect...
tools/auto_bisect/bisect.cfg:72: 'builder_port': '8341',
This shouldn't be submitted, it's only just for testing to make sure everything
still works on the bisect bots.

https://codereview.chromium.org/564663002/diff/20001/tools/auto_bisect/bisect...
File tools/auto_bisect/bisect_perf_regression.py (right):

https://codereview.chromium.org/564663002/diff/20001/tools/auto_bisect/bisect...
tools/auto_bisect/bisect_perf_regression.py:2293: good_revision =
self.source_control.GetCommitPosition(good_revision)
revision_to_check was not referenced. Pylint caught this.

[qyearsley, 2014-09-11 16:39:53]

This CL isn't directly related to supporting full builds and functional bisects,
so it's just FYI for Ojan & Sergiy.

Submitting this could wait until Prasad's current CLs are submitted.

[tonyg, 2014-09-16 00:36:02]

lgtm

[qyearsley, 2014-09-19 20:05:52]

On 2014/09/16 00:36:02, tonyg wrote:
> lgtm

Update on this CL: I'm running into an issue now where in Gathering Reference
Values, syncing to the first revision the build and test for is failing.

http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_9_perf_bi...

This might still be an issue with a path that needs to be updated; I want to
look into that today.

[qyearsley, 2014-09-25 23:05:47]

Yay! With Prasad's help, I realized that self.src_cwd in
BisectPerformanceMetrics isn't the source directory that the script is running
from, but instead it's the src directory in the checked out chromium repository
(in the bisect/ directory which is created when running a bisect job).

After reverting this self.src_dir to how it was before, I got a successful try
job run.

[qyearsley, 2014-09-25 23:05:50]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-09-25 23:08:54]

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

[commit-bot: I haz the power, 2014-09-25 23:22:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-25 23:22:13]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[qyearsley, 2014-09-25 23:51:39]

The CQ bit was checked by qyearsley@chromium.org

[commit-bot: I haz the power, 2014-09-25 23:53:29]

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

[commit-bot: I haz the power, 2014-09-26 01:19:44]

Committed patchset #13 (id:240001) as fc6a61c6dad6ca8865bd90028003d4c8bf20ae77

[commit-bot: I haz the power, 2014-09-26 01:20:15]

Patchset 13 (id:??) landed as
https://crrev.com/62edbcf1e8e5dd1386693b7b4b90169e72bd7300
Cr-Commit-Position: refs/heads/master@{#296847}