aboutsummaryrefslogtreecommitdiffhomepage
path: root/dm
diff options
context:
space:
mode:
authorGravatar mtklein <mtklein@chromium.org>2014-08-05 07:19:46 -0700
committerGravatar Commit bot <commit-bot@chromium.org>2014-08-05 07:19:46 -0700
commit36ea6c81c2a249ef344d438943050ec960631f0d (patch)
tree834d7907957e7f32acc46158a4b17668a5f78406 /dm
parent838f62db0a77487f6732ed13a0972a1e646ae16a (diff)
For some reason, starting tests before gms makes DM run much faster.
Must be getting the path ops tests going early helps? On my desktop, Release: 50s -> 24s Debug: 62s -> 40s BUG=skia: R=bsalomon@google.com, mtklein@google.com Author: mtklein@chromium.org Review URL: https://codereview.chromium.org/435423003
Diffstat (limited to 'dm')
-rw-r--r--dm/DM.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/dm/DM.cpp b/dm/DM.cpp
index 76dc4148ed..6256d0d856 100644
--- a/dm/DM.cpp
+++ b/dm/DM.cpp
@@ -234,8 +234,8 @@ int dm_main() {
gms.count(), configs.count(), tests.count(), skps.count());
DM::Reporter reporter;
DM::TaskRunner tasks(FLAGS_threads, FLAGS_gpuThreads);
- kick_off_gms(gms, configs, gpuAPI, *expectations, &reporter, &tasks);
kick_off_tests(tests, &reporter, &tasks);
+ kick_off_gms(gms, configs, gpuAPI, *expectations, &reporter, &tasks);
kick_off_skps(skps, &reporter, &tasks);
tasks.wait();