New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 741816 link

Starred by 2 users
Status: Assigned
Owner:
isherman@chromium.org
Cc:
skare@chromium.org
isherman@chromium.org
asvitk...@chromium.org
█ rkaplow@chromium.org
Components:
EstimatedDays: ----
NextAction: 2017-07-19
OS: All
Pri: 3
Type: Task



Sign in to add a comment

Verify that startup metrics are not changed by recording them sooner

Project Member Reported by isherman@chromium.org, Jul 12 2017 
In https://codereview.chromium.org/2955063005/, I'm changing the timing at which startup metrics are recorded, to potentially occur earlier in startup.  This is not expected to change the metrics.  We should verify that's the case after the CL lands.
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 12 2017 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2d71d53f0142954869b02fb1a93d8c790e1743c3

commit 2d71d53f0142954869b02fb1a93d8c790e1743c3
Author: isherman <isherman@chromium.org>
Date: Wed Jul 12 21:54:55 2017

[Cleanup] Migrate ChromeBrowserMainExtraPartsMetrics to use the Task Scheduler.

This also changes the timing with which startup metrics are recorded: Previously they were recorded ~45 seconds after startup; now they're recorded whenever the TaskScheduler schedules them to be.  This is not expected to change the values recorded to these metrics.

BUG= 667892 , 741816
TEST=none
R=asvitkine@chromium.org

Review-Url: https://codereview.chromium.org/2955063005
Cr-Commit-Position: refs/heads/master@{#486114}

[modify] https://crrev.com/2d71d53f0142954869b02fb1a93d8c790e1743c3/chrome/browser/metrics/chrome_browser_main_extra_parts_metrics.cc

Comment 2 by monor...@bugs.chromium.org, Jul 19 2017 

The NextAction date has arrived: 2017-07-19
►

Sign in to add a comment