telemetry: Add python mock library.

telemetry: Add python mock library.

This is the mock library used by ChromeOS, and it comes bundled with Python
3.3+.

BUG=

Committed: https://crrev.com/bf655124b7ec1836216411173f6c329b0ed1935f
Cr-Commit-Position: refs/heads/master@{#315653}

[erikchen, 2015-02-09 23:54:25]

Patchset #1 (id:1) has been deleted

[erikchen, 2015-02-10 00:23:51]

erikchen@chromium.org changed reviewers:
+ nednguyen@google.com

[erikchen, 2015-02-10 00:23:52]

nednguyen: Please review.

[nednguyen, 2015-02-10 00:30:50]

nednguyen@google.com changed reviewers:
+ dtu@chromium.org, sullivan@chromium.org

[nednguyen, 2015-02-10 00:30:51]

+Dave: is this the right way to add third party library? Erik is adding mock
library to do his unittest, rather than use our homegrown hacky way of doing
mock.

[sullivan, 2015-02-10 14:58:59]

On 2015/02/10 00:30:51, nednguyen wrote:
> +Dave: is this the right way to add third party library? Erik is adding mock
> library to do his unittest, rather than use our homegrown hacky way of doing
> mock.

Note: this is the same library the perf dashboard uses for its python tests, so
we'll be headed in the same direction when we merge into the same repo.

I'm also curious why we use a homegrown mock library.

[dtu, 2015-02-10 20:54:27]

On 2015/02/10 14:58:59, sullivan wrote:
> On 2015/02/10 00:30:51, nednguyen wrote:
> > +Dave: is this the right way to add third party library? Erik is adding mock
> > library to do his unittest, rather than use our homegrown hacky way of doing
> > mock.
> 
> Note: this is the same library the perf dashboard uses for its python tests,
so
> we'll be headed in the same direction when we merge into the same repo.
> 
> I'm also curious why we use a homegrown mock library.

This is nice. lgtm with one comment.

I wanted to add a mock library about a year ago, but Nat wanted something more
lightweight?

[dtu, 2015-02-10 20:54:33]

https://codereview.chromium.org/910093002/diff/10001/tools/telemetry/third_pa...
File tools/telemetry/third_party/mock/README.chromium (right):

https://codereview.chromium.org/910093002/diff/10001/tools/telemetry/third_pa...
tools/telemetry/third_party/mock/README.chromium:5: Date: 2015-02-09
This is the date the package was updated. You can also omit it because the
version is supplied.

[erikchen, 2015-02-10 21:03:10]

New patchsets have been uploaded after l-g-t-m from dtu@chromium.org

[erikchen, 2015-02-10 21:03:24]

https://codereview.chromium.org/910093002/diff/10001/tools/telemetry/third_pa...
File tools/telemetry/third_party/mock/README.chromium (right):

https://codereview.chromium.org/910093002/diff/10001/tools/telemetry/third_pa...
tools/telemetry/third_party/mock/README.chromium:5: Date: 2015-02-09
On 2015/02/10 20:54:33, dtu wrote:
> This is the date the package was updated. You can also omit it because the
> version is supplied.

Done.

[erikchen, 2015-02-10 21:03:27]

The CQ bit was checked by erikchen@chromium.org

[commit-bot: I haz the power, 2015-02-10 21:04:48]

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

[commit-bot: I haz the power, 2015-02-10 22:00:22]

Committed patchset #2 (id:30001)

[commit-bot: I haz the power, 2015-02-10 22:01:02]

Patchset 2 (id:??) landed as
https://crrev.com/bf655124b7ec1836216411173f6c329b0ed1935f
Cr-Commit-Position: refs/heads/master@{#315653}