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

Issue 865998 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Closed: Oct 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 863813



Sign in to add a comment

Dashboard - Migrate builder data

Project Member Reported by simonhatch@chromium.org, Jul 20

Issue description

This is coming out of the postmortem for the OBBS failures, we need to migrate all bot data from the old -> new names for the following bots:


These are using the new naming scheme, v2.

android-nexus5X -> android-nexus-5X-perf
Win 10 Perf -> win-10-perf


These are using the old new naming scheme, v1.

android-nexus-5 -> Android Nexus5 Perf
android-webview-nexus5X -> Android Nexus5X WebView Perf
android-webview-nexus6 -> Android Nexus6 WebView Perf
android-one -> Android One Perf


These we can just ignore?

Win 10 High-DPI Perf
Win 7 Nvidia GPU Perf
Win 7 Perf



We should probably write some migration of page_states too.


Ned, can you check that list is right?
 
Blocking: 863813
Owner: nednguyen@chromium.org
Status: Assigned (was: Untriaged)
Passing to Ned for confirmation on names, pass back to me once confirmed or corrected
Owner: simonhatch@chromium.org
We also ignore "Android Nexus5 Perf", "Android Nexus5X WebView Perf", "Android Nexus6 WebView Perf", "Android One Perf".

Only android-nexus5X & "Win 10 Perf" need to be renamed.
What are the perf bots currently uploading to? android-nexus5 or Android Nexus5 Perf? For teams like v8 that might be looking at the graphs and want all the data in one spot, shoudln't we still do those migrations for now even if the bots will be discontinued?
Ah, I misunderstood your question. Yet, we will also need:
android-nexus-5 -> Android Nexus5 Perf
android-webview-nexus5X -> Android Nexus5X WebView Perf
android-webview-nexus6 -> Android Nexus6 WebView Perf
android-one -> Android One Perf

Ok so that initial list I posted, that's ok? If so I'll proceed with first bots.
Yes. Sorry for the confusion!
Cc: cbruni@chromium.org ushesh@chromium.org
Ok head's up I'm going to start some of these migrations. They'll take a while, will probably space them out over the next week. I'll also try to migrate the page_states themselves, so that existing reports will continue to work.
The first section is not quite right. For the bots using the new naming scheme, V2, recall that these bots were renamed twice:

android-nexus5X -> android-nexus-5X-perf
Android Nexus 5X Perf -> android-nexus-5X-perf
chromium-rel-win10 -> win-10-perf
Win 10 Perf -> win-10-perf

Also why can we ignore the other Windows bots? Is it because v8 didn't complain about Windows?
I think I got confused and thought those bots were discontinued entirely, but looks like they're still online. So slight tweak to this list:


Naming scheme, v2.

android-nexus5X -> android-nexus-5X-perf
Android Nexus 5X Perf -> android-nexus-5X-perf
Win 10 Perf -> win-10-perf
chromium-rel-win10 -> win-10-perf


These are using the old new naming scheme, v1.

android-nexus-5 -> Android Nexus5 Perf
android-webview-nexus5X -> Android Nexus5X WebView Perf
android-webview-nexus6 -> Android Nexus6 WebView Perf
android-one -> Android One Perf

win-high-dpi -> Win 10 High-DPI Perf
chromium-rel-win7-gpu-nvidia -> Win 7 Nvidia GPU Perf
chromium-rel-win7-dual -> Win 7 Perf



Right now the android-one is being migrated, and I'm writing a quick endpoint to do page_state migrations so that everyone's reports will continue working even if they're referencing the old bot names.
Cc: mlamouri@chromium.org
So FYI this is still going on.
Status: Fixed (was: Assigned)
Completed a while back.

Sign in to add a comment