diff options
author | dpranke <dpranke@chromium.org> | 2015-10-02 18:11:34 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-10-03 01:12:27 +0000 |
commit | 751516abefd8b10853c103c563345b5e04de970d (patch) | |
tree | 3b2b8c048a29763db4d322001ef22a7fc1a1a812 /ash/utility | |
parent | bff95df97471b53dbe2f540d0b3475d9dc32d50c (diff) | |
download | chromium_src-751516abefd8b10853c103c563345b5e04de970d.zip chromium_src-751516abefd8b10853c103c563345b5e04de970d.tar.gz chromium_src-751516abefd8b10853c103c563345b5e04de970d.tar.bz2 |
Add MB commands for generating isolates and running them.
Since the logic for handling isolates in GN is split between
the GN and MB tools, it's harder to build and test isolates
with GN than it is with GYP (where you can just say 'ninja base_unittests_run'
to build the isolate).
This patch adds two new commands to the MB tool to make things easier.
The first is `mb isolate`, which is the equivalent of the
GYP _run targets: it creates the .isolate and .isolated.gen.json files.
The second is `mb run`, which is a convenient wrapper command that
runs mb isolate, runs ninja to ensure that the test is actually built
and up-to-date, and then runs the swarming_client commands to actually
run the test locally (in an isolated directory).
Both commands will work either off of an existing build directory or
in a new directory (if given the -m/-b or -c flags).
R=kbr@chromium.org
BUG=
Review URL: https://codereview.chromium.org/1370373005
Cr-Commit-Position: refs/heads/master@{#352217}
Diffstat (limited to 'ash/utility')
0 files changed, 0 insertions, 0 deletions