Add --enable-automation flag in GetFromBrowserOptions()
crrev.com/c/956654 introduced the bad flags warning of "stability and
security will suffer" for Android.
This change caused parformance regressions because a bad flag
"--ignore-certificate-errors-spki-list" is used for perfomance testing.
(crbug.com/822258#c13)
So crrev.com/c/965727 introduces the check of "--enable-automation" flag in ShowBadFlagsPrompt().
(This check already exists in startup_browser_creator_impl.cc for Desktop not
to show the infobar during performance tests.)
This CL adds the flag to GetFromBrowserOptions().
Bug: chromium:822258
Change-Id: I8a07c88960678877ee1add1c0d29ad323611a816
Reviewed-on: https://chromium-review.googlesource.com/965712
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
diff --git a/telemetry/telemetry/internal/backends/chrome/chrome_startup_args.py b/telemetry/telemetry/internal/backends/chrome/chrome_startup_args.py
index 213b993..31cde85 100644
--- a/telemetry/telemetry/internal/backends/chrome/chrome_startup_args.py
+++ b/telemetry/telemetry/internal/backends/chrome/chrome_startup_args.py
@@ -41,6 +41,9 @@
args.append('--no-default-browser-check')
args.append('--no-first-run')
+ # Not to show info bars which interfere with tests that assume no info bars.
+ args.append('--enable-automation')
+
# Turn on GPU benchmarking extension for all runs. The only side effect of
# the extension being on is that render stats are tracked. This is believed
# to be effectively free. And, by doing so here, it avoids us having to
