Allow browser tests to run with dynamic CLD data.

chrome/browser/component_updater/cld_component_installer.cc

Index: chrome/browser/component_updater/cld_component_installer.cc
diff --git a/chrome/browser/component_updater/cld_component_installer.cc b/chrome/browser/component_updater/cld_component_installer.cc
index 195f25301eb03d615b0c94c1fe6e5a4b666ad9db..cc89d6bc33ad4dafbe74bf08da1ae10478fa1daa 100644
--- a/chrome/browser/component_updater/cld_component_installer.cc
+++ b/chrome/browser/component_updater/cld_component_installer.cc
@@ -29,8 +29,8 @@ namespace {
 // make the path available to other parts of the system such as the
 // translation libraries. We create a global to hold onto the path, and a
 // lock to guard it. See GetLatestCldDataFile(...) for more info.
-base::LazyInstance<base::Lock> cld_file_lock = LAZY_INSTANCE_INITIALIZER;
-base::LazyInstance<base::FilePath> cld_file = LAZY_INSTANCE_INITIALIZER;
+static base::LazyInstance<base::Lock> cld_file_lock = LAZY_INSTANCE_INITIALIZER;

[Sorin Jianu, 2014/05/15 17:16:13]

Is there a reason we have the static keyword here?

In general static is not needed in these declarations (these members already
have file scope and their visibility is restricted to this module due to the
anon namespace).

[Andrew Hayden (chromium.org), 2014/05/16 17:53:20]

Done.

+static base::LazyInstance<base::FilePath> cld_file = LAZY_INSTANCE_INITIALIZER;
 
 }