Add chrome.isolate and chrome_run gyp target.

Add chrome.isolate and chrome_run gyp target.

This permits a user to archive a working chrome build on isolateserver for
downloading it elsewhere. Note that the actual list of files listed
chrome.isolate hasn't been verified but I prefer to commit it as-is and check
each OS afterward. In particular, this new chrome_run target is not included in
chromium_swarm_tests.

Command to archive is:
  ninja -C out/Release chrome_run
  python tools/swarm_client/isolate.py hashtable \
      -s out/Release/chrome.isolated \
      -o https://isolateserver-dev.appspot.com/
  sha1sum out/Release/chrome.isolated

Command to download is:
  python tools/swarm_client/run_isolated.py \
      -r https://isolateserver-dev.appspot.com/content/retrieve/default-gzip/ \
      -H <hash got from sha1sum command above>/ \
      --download <path to download files>

Note that the same command can be used on all OSes, except for sha1sum on
Windows.

R=csharp@chromium.org
BUG=98636
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=194010

[M-A Ruel, 2013-04-09 22:02:03]

Note that I don't specify a command here, since we don't want it to be run by
error and it's not a process that has a finite runtime like a test, it just a
browser after all. :)

[csharp, 2013-04-10 13:09:03]

lgtm

Would the plan be to then include this file for the other  isolate files that
use the browser? (such as browser_tests)

[commit-bot: I haz the power, 2013-04-10 14:01:00]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/13913025/1

[commit-bot: I haz the power, 2013-04-10 14:01:05]

Presubmit check for 13913025-1 failed and returned exit status 1.

INFO:root:Found 2 file(s).

Running presubmit commit checks ...
Running /b/commit-queue/workdir/chromium/PRESUBMIT.py
Running /b/commit-queue/workdir/chromium/chrome/PRESUBMIT.py

** Presubmit Messages **
If this change has an associated bug, add BUG=[bug number].

** Presubmit ERRORS **
Missing LGTM from an OWNER for these files:
    chrome/chrome_exe.gypi

[M-A Ruel, 2013-04-10 17:24:15]

On 2013/04/10 13:09:03, csharp wrote:
> lgtm
> 
> Would the plan be to then include this file for the other  isolate files that
> use the browser? (such as browser_tests)

Not on the short-to-mid term. The reason is that supporting that will require a
significant effort when isolate.py tries to rewrite a .isolate file; it has to
know about where each single dependency was specified and it would require
significantly more complex code to manage that. Also this would eventually
increase the cognitive overhead to figure how which files are actually mapped
since multiple files would have to be looked up. So I'm postponing that for now.

This CL only pertains to archiving chrome and downloading it somewhere else for
testing. The main use case is someone wanting to test on XP; you can build
locally or on the try server and download it easily on an XP workstation, only
run_isolated.py and python are needed!

[M-A Ruel, 2013-04-10 17:25:20]

+ Nico for OWNERS.

[Nico, 2013-04-11 05:02:28]

lgtm stamp, but you really should have a tracking bug for this isolate stuff

[M-A Ruel, 2013-04-12 16:06:05]

On 2013/04/11 05:02:28, Nico wrote:
> lgtm stamp, but you really should have a tracking bug for this isolate stuff

I added the meta-bug 98636, but it's seriously meta.

[commit-bot: I haz the power, 2013-04-12 16:06:23]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/13913025/1

[commit-bot: I haz the power, 2013-04-12 19:27:46]

Retried try job too often on linux_rel for step(s) unit_tests
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=linux_rel&...

[commit-bot: I haz the power, 2013-04-12 20:38:35]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/maruel@chromium.org/13913025/1

[commit-bot: I haz the power, 2013-04-12 20:58:32]

Change committed as 194010