[cros] RLZ tracking can be turned off via a flag file.

chrome/browser/chromeos/chrome_browser_main_chromeos.cc

Index: chrome/browser/chromeos/chrome_browser_main_chromeos.cc
diff --git a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
index 0fc08e52714519b58a083013b27be6c969c3569c..1d7c829bee7e1906f2d64424bd98905cabfbca16 100644
--- a/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
+++ b/chrome/browser/chromeos/chrome_browser_main_chromeos.cc
@@ -70,6 +70,7 @@
 #include "chrome/browser/prefs/pref_service.h"
 #include "chrome/browser/profiles/profile.h"
 #include "chrome/browser/profiles/profile_manager.h"
+#include "chrome/browser/rlz/rlz.h"
 #include "chrome/browser/signin/token_service_factory.h"
 #include "chrome/browser/system_monitor/removable_device_notifications_chromeos.h"
 #include "chrome/common/chrome_notification_types.h"
@@ -496,6 +497,11 @@ void ChromeBrowserMainPartsChromeos::PreProfileInit() {
                                   &tracker_);
 #endif
 
+#if defined(ENABLE_RLZ)
+  if (parsed_command_line().HasSwitch(::switches::kTestType))
+    RLZTracker::EnableZeroDelayForTesting();

[Peter Kasting, 2012/12/17 20:14:03]

Must we call this here?  Can we instead enable in individual tests that care, as
you've already done elsewhere in this CL?

[Ivan Korotkov, 2012/12/20 09:20:42]

I'd like to leave it here (like WizardController::SetZeroDelays in
PostProfileInit) because otherwise any browser test that uses real LoginUtils
and calls GetBlockingPool()->FlushForTesting() will be slowed down by 20 seconds
without an obvious reason.
login_utils_browsertest doesn't go through this path (it's not a real
InProcessBrowserTest, despite it's name), so a separate call is needed there.

[Peter Kasting, 2012/12/20 19:32:00]

Then can we make one of the following happen instead:
* In testing mode, the RLZ tracker _always_ runs in zero-delay mode (i.e. we do
this check in the RLZ code itself).
* In testing mode, the RLZ tracker doesn't do anything at all unless you
explicitly enable it, or perhaps DCHECKs or something.

Either one of these is better than having some somewhat random code added to the
startup functions; startup is so hairy we should go to great lengths to avoid
making it do anything further.

[Ivan Korotkov, 2012/12/21 09:59:48]

Ok, let's do the 1st option.

+#endif
+
   // In Aura builds this will initialize ash::Shell.
   ChromeBrowserMainPartsLinux::PreProfileInit();
 }
@@ -521,6 +527,9 @@ void ChromeBrowserMainPartsChromeos::PostProfileInit() {
         profile()->GetPrefs()->FindPreference(prefs::kUseSharedProxies);
     if (use_shared_proxies_pref->IsDefaultValue())
       profile()->GetPrefs()->SetBoolean(prefs::kUseSharedProxies, false);
+
+    // This is done in LoginUtils::OnProfileCreated during normal login.
+    LoginUtils::Get()->InitRlzDelayed(profile());
   }
 
   // Make sure the NetworkConfigurationUpdater is ready so that it pushes ONC