From c96d5309cee28f5b839e10ba9525fdfc6913a61c Mon Sep 17 00:00:00 2001 From: "jar@chromium.org" Date: Tue, 24 Feb 2009 01:25:06 +0000 Subject: Re-re-roll use of ongoing logs to gather stability metrics This was rolled back to try to use only the initial logs to gather statibility stats, because we were having trouble capturing data in ongoing logs. We now resolved the problem (which was actually only on the stability branch), so we'll roll back to using this method and verify it in the dev branch. tbr=mal Review URL: http://codereview.chromium.org/27061 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@10238 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/metrics/metrics_service.cc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'chrome/browser/metrics') diff --git a/chrome/browser/metrics/metrics_service.cc b/chrome/browser/metrics/metrics_service.cc index 4d34ebb..42fae63 100644 --- a/chrome/browser/metrics/metrics_service.cc +++ b/chrome/browser/metrics/metrics_service.cc @@ -748,9 +748,7 @@ void MetricsService::StopRecording(MetricsLog** log) { // end of all log transmissions (initial log handles this separately). // Don't bother if we're going to discard current_log_. if (log) { - // TODO(jar): when initial logs and ongoing logs have equal survivability, - // uncomment the following line to expedite stability data uploads. - // current_log_->RecordIncrementalStabilityElements(); + current_log_->RecordIncrementalStabilityElements(); RecordCurrentHistograms(); } -- cgit v1.1