Perf test to measure loading CDM library.

chrome/chrome_tests.gypi

Index: chrome/chrome_tests.gypi
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi
index 3ed45f56ee884a77d37e5e8186a5b6194683ec85..ccc0e00c1834e51d10d0bb22f74cd8cb9eaa1ff1 100644
--- a/chrome/chrome_tests.gypi
+++ b/chrome/chrome_tests.gypi
@@ -898,6 +898,24 @@
     },
     {
       # Executable that runs each browser test in a new process.

[ddorwin, 2014/02/06 19:57:33]

Update the comment.

+      'target_name': 'cdm_load_perf_test',
+      'type': '<(gtest_target_type)',
+      'dependencies': [
+        '../base/base.gyp:base',
+        #'../base/base.gyp:test_support_base',

[ddorwin, 2014/02/06 19:57:33]

remove these commented items

+        '../base/base.gyp:test_support_perf',
+        '../testing/gmock.gyp:gmock',

[ddorwin, 2014/02/06 19:57:33]

Do we need GMock?

+        '../testing/gtest.gyp:gtest',
+        'test/perf/perf_test.gyp:*',
+        #'../skia/skia.gyp:skia',
+      ],
+      'sources': [
+        'browser/media/load_cdm_benchmark_test.cc',
+      ]
+
+    },
+    {
+      # Executable that runs each browser test in a new process.
       'target_name': 'browser_tests',

[ddorwin, 2014/02/06 19:57:33]

Should this test really come before browser_tests in this file? The latter seems
more common and like it should come earlier. The other perf tests are much
farther down in this file.

       'type': 'executable',
       'dependencies': [