Issue metadata
Sign in to add a comment
|
migrate dashboard data from "Linux Perf" to "linux-perf" |
||||||||||||||||||||||
Issue descriptionWe migrated "Linux Perf" on the chromium.perf dashbaord to "linux-perf" and the data needs to be migrated for bisects to succeed.
,
Apr 30 2018
The perf-id is now updated to be the configuration name: crbug.com/817823 I was under the impression that the bot was a part of the unique path to the time series, but obviously you know more than I do there.
,
Apr 30 2018
Hmm not sure a migration is necessary for bisects to succeed, Pinpoint was already updated with data on linux-perf so any new anomalies that come in should work. I think a migration is only necessary if you want to retain the old data, if that's the case then we can probably drop this to a p2 or something.
,
May 2 2018
This is not necessary for successful bisects, it is only if we want data continuation in the graphs. Lowering priority.
,
May 4 2018
Ran the migration this afternoon, surprisingly only took 2-3 hours. Everything seems to be on linux-perf now.
,
Jun 28 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by simonhatch@chromium.org
, Apr 30 2018