Add telemetry_gpu_unittests.isolate.

Add telemetry_gpu_unittests.isolate.

This will make it easier to run this test suite on the bots.

Refactored Telemetry isolates into:

  - telemetry.isolate: contains just Telemetry's logic and
    dependencies (bitmaptools). Moved this from chrome/ into content/
    to match its dependencies.

  - telemetry_chrome_test.isolate: describes Telemetry tests which run
    using the Chromium browser. Currently telemetry_gpu_test.isolate
    is the only consumer of this isolate.

The new test target will be added to the bots in a subsequent commit;
some more work is needed to do so.

BUG=495868
R=zmo@chromium.org,phajdan.jr@chromium.org,maruel@google.com
TBR=maruel@chromium.org

Committed: https://crrev.com/57cf0faa30d1fed831fcddd9b6b07049582091ae
Cr-Commit-Position: refs/heads/master@{#336392}

[Ken Russell (switch to Gerrit), 2015-06-25 23:47:45]

kbr@chromium.org changed reviewers:
+ bajones@chromium.org, zmo@google.com

[Ken Russell (switch to Gerrit), 2015-06-25 23:52:40]

kbr@chromium.org changed reviewers:
+ csharp@chromium.org, eakuefner@chromium.org, maruel@chromium.org,
nednguyen@google.com, phajdan.jr@chromium.org

[Ken Russell (switch to Gerrit), 2015-06-25 23:52:41]

bajones/zmo: please review
maruel or csharp: please review .isolate changes
phjadan.jr: please review and advise on the overall approach

This adds a new isolate for the script src/content/test/gpu/run_unittests.py so
that it can be run more easily on the bots.

I'm hoping that by doing so this can be invoked like the other swarmed gtests in
src/testing/buildbot, rather than needing a new script like the other Telemetry
scripts.

Please tell me if it looks like this is entirely on the wrong track.

I've tested the built telemetry_gpu_unittests isolate.

[Zhenyao Mo, 2015-06-25 23:54:41]

On 2015/06/25 23:47:46, Ken Russell wrote:

LGTM

[Marc-Antoine Ruel (Google), 2015-06-26 02:10:40]

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

[Marc-Antoine Ruel (Google), 2015-06-26 02:10:41]

that sounds good, lgtm

https://codereview.chromium.org/1212113003/diff/20001/content/telemetry_gpu_u...
File content/telemetry_gpu_unittests.isolate (right):

https://codereview.chromium.org/1212113003/diff/20001/content/telemetry_gpu_u...
content/telemetry_gpu_unittests.isolate:17: '../content/test/gpu/',
I'd prefer to have the list sorted, e < h.

[Paweł Hajdan Jr., 2015-06-26 13:10:05]

phajdan.jr@chromium.org changed reviewers:
+ zmo@chromium.org

[Paweł Hajdan Jr., 2015-06-26 13:10:05]

LGTM just in case

For me this change doesn't seem to make anything easier or harder. You'd likely
need a dedicated class in
build/scripts/slave/recipe_modules/chromium_tests/steps.py since
src/testing/scripts infrastructure doesn't support swarming (I think we'd get
that by moving recipes to repos, a project luqui is working on).

[Ken Russell (switch to Gerrit), 2015-06-26 15:36:11]

On 2015/06/26 13:10:05, Paweł Hajdan Jr. wrote:
> LGTM just in case
> 
> For me this change doesn't seem to make anything easier or harder. You'd
likely
> need a dedicated class in
> build/scripts/slave/recipe_modules/chromium_tests/steps.py since
> src/testing/scripts infrastructure doesn't support swarming (I think we'd get
> that by moving recipes to repos, a project luqui is working on).

Looking again at sergiyb@'s work to swarm the Telemetry based GPU tests in
scripts/slave/recipe_modules/chromium_tests/steps.py, I think it shouldn't be
hard to refactor it to support swarming all of the Telemetry based tests
(including telemetry_unittests and telemetry_perf_unittests). I'll look into
this next.

[Ken Russell (switch to Gerrit), 2015-06-26 15:36:17]

The CQ bit was checked by kbr@chromium.org

[commit-bot: I haz the power, 2015-06-26 15:37:05]

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

[commit-bot: I haz the power, 2015-06-26 15:45:28]

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

[commit-bot: I haz the power, 2015-06-26 15:45:29]

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

[Ken Russell (switch to Gerrit), 2015-06-26 16:55:00]

maruel@: looks like you lgtm'd this from the wrong account. I'm TBR'ing it to
you.

[Ken Russell (switch to Gerrit), 2015-06-26 16:55:34]

The CQ bit was checked by kbr@chromium.org

[commit-bot: I haz the power, 2015-06-26 16:56:44]

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

[commit-bot: I haz the power, 2015-06-26 17:04:48]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-06-26 17:05:53]

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

[M-A Ruel, 2015-06-26 18:06:23]

On 2015/06/26 16:55:00, Ken Russell wrote:
> maruel@: looks like you lgtm'd this from the wrong account. I'm TBR'ing it to
> you.

oops, lgtm.