New issue
Advanced search Search tips

Issue 838132 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug-Regression

Blocking:
issue 836037



Sign in to add a comment

migrate dashboard data from "Linux Perf" to "linux-perf"

Project Member Reported by eyaich@chromium.org, Apr 30 2018

Issue description

We migrated "Linux Perf" on the chromium.perf dashbaord to "linux-perf" and the data needs to be migrated for bisects to succeed.
 
Why does data need to be migrated for bisects to succeed?

Comment 2 by eyaich@chromium.org, 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.
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.
Labels: -Pri-1 Pri-3
This is not necessary for successful bisects, it is only if we want data continuation in the graphs.  Lowering priority.
Ran the migration this afternoon, surprisingly only took 2-3 hours. Everything seems to be on linux-perf now.
Status: Fixed (was: Untriaged)

Sign in to add a comment