diff options
| author | dpranke@chromium.org <dpranke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-15 14:23:21 +0000 |
|---|---|---|
| committer | dpranke@chromium.org <dpranke@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-08-15 14:25:59 +0000 |
| commit | 6707442fb64e2f00ed30352309c03137ca046fcb (patch) | |
| tree | 6ae470ee4fa7fcff9ad91e3ecb02aa59e0c9bf10 /sync/internal_api/public | |
| parent | 16a4206fa5c288cae557309927a5c1b78e030b4d (diff) | |
| download | chromium_src-6707442fb64e2f00ed30352309c03137ca046fcb.zip chromium_src-6707442fb64e2f00ed30352309c03137ca046fcb.tar.gz chromium_src-6707442fb64e2f00ed30352309c03137ca046fcb.tar.bz2 | |
Change gtest launcher, telemetry unittests to run in parallel and retry failures by default.
Previously, gtest-based tests would not run tests in parallel or retry failures
by default unless you specified the --test-launcher-bot-mode flag
This patch changes the behavior so that we run tests in parallel and retry failures by
default if we are running *all* of the tests (i.e., --gtest_filter was *not* specified).
You can still pass --test-launcher-jobs=X to control how many tests run in parallel,
and --test-launcher-retry-limit=0 to turn retries off and
--test-launcher-retry-limit=X to control how many times to retry.
R=jam@chromium.org, phajdan.jr@chromium.org, ojan@chromium.org, tonyg@chromium.org
BUG=402089
Review URL: https://codereview.chromium.org/469533002
Cr-Commit-Position: refs/heads/master@{#289839}
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289839 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/internal_api/public')
0 files changed, 0 insertions, 0 deletions