summaryrefslogtreecommitdiffstats
path: root/build
diff options
context:
space:
mode:
authorjessicag <jessicag@chromium.org>2016-03-11 14:34:49 -0800
committerCommit bot <commit-bot@chromium.org>2016-03-11 22:37:09 +0000
commitab7a08b61e58d1a50565cb892f3402cebafbcf16 (patch)
tree025d6fd32136b80f6480b3ef7f230aaa838a564b /build
parentb6c83fa8177e35559eb4b0bc3ee51eb76f7ef337 (diff)
downloadchromium_src-ab7a08b61e58d1a50565cb892f3402cebafbcf16.zip
chromium_src-ab7a08b61e58d1a50565cb892f3402cebafbcf16.tar.gz
chromium_src-ab7a08b61e58d1a50565cb892f3402cebafbcf16.tar.bz2
Add support for Blimp engine metrics reporting in development.
Currently there is no way of recording or reporting metrics for the Blimp engine. To collect metrics for the Blimp engine in development two things are required. First, for metrics recording and reporting to be enabled on the Blimp engine. Second, for the metrics logging to flag Blimp engine reports so they can be filtered from other linux metrics reports. These code behavior changes are currently kept between a single build arg, but are controlled via separate defines checks. These changes will allow metrics to be collected on development instances of Blimp and viewed separately from Linux builds. BUG=592757 Review URL: https://codereview.chromium.org/1765293002 Cr-Commit-Position: refs/heads/master@{#380760}
Diffstat (limited to 'build')
-rw-r--r--build/args/blimp_engine.gn3
1 files changed, 2 insertions, 1 deletions
diff --git a/build/args/blimp_engine.gn b/build/args/blimp_engine.gn
index b78ba7a..ef990cd60 100644
--- a/build/args/blimp_engine.gn
+++ b/build/args/blimp_engine.gn
@@ -9,9 +9,10 @@
use_aura = true
use_ozone = true
+metrics_use_blimp = true
# Not available within docker container.
use_alsa = false
use_pulseaudio = false
use_cups = false
-use_glib = false \ No newline at end of file
+use_glib = false