New issue
Advanced search Search tips

Issue 774647 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 700160
issue 713335



Sign in to add a comment

Migrate test data from tough_video_cases name to media name.

Project Member Reported by crouleau@chromium.org, Oct 13 2017

Issue description

Hi Simon, 

I'm trying to do a test names migration ( https://chromeperf.appspot.com/migrate_test_names ) from 

*/*/media.tough_video_case_tbmv2/*/*
to 
*/*/media.desktop/*/*

And the "Run Migration" button is greyed out. 

See https://bugs.chromium.org/p/chromium/issues/detail?id=713335#c26 for similar situation. We really just want to migrate the data as is from one benchmark name to another.

If I click "List tests" it runs the spinner and then doesn't do anything. The console does not log anything either.
 
Owner: simonhatch@chromium.org
Will take this for now to investigate what's up with the page.
Owner: crouleau@chromium.org
*/*/media.tough_video_case_tbmv2/*/* -> */*/media.tough_video_cases_tbmv2/*/*

Btw that pattern seems to timeout, so you'll likely need to migrate each bot. Ie.

ChromiumPerf/chromium-rel-mac11/media.tough_video_cases_tbmv2/*/*
ChromiumPerf/chromium-rel-mac11-pro/media.tough_video_cases_tbmv2/*/*
etc...
So I just realized that the test path you're using doesn't need to be so deep:

*/*/media.tough_video_cases_tbmv2/*

All the children of that, ie. */*/media.tough_video_cases_tbmv2/*/bar will be moved


So you can run a migration on each bot:

*/chromium-rel-mac11/media.tough_video_cases_tbmv2/*
*/chromium-rel-mac11-pro/media.tough_video_cases_tbmv2/*
etc.
I queued up migrations one-by-one for chromium-rel-mac-retina 
chromium-rel-mac11 
chromium-rel-mac11-air 
chromium-rel-mac11-pro 
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel .
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual 
chromium-rel-win8-dual 
linux-release 
win-high-dpi
win-zenbook 
chromium-rel-win7-gpu-intel
chromium-win-clang
chromium-win-clang-ref
mac-test-retina
win-10-4-core-low-end
win-10-low-end
win-power-high-dpi

Now I will tackle Android.
Status: Fixed (was: Assigned)
I queued up Android: 

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2
android-one
android-webview-nexus5X
android-webview-nexus6
fyi-android-power-nexus-5x
fyi-android-swarming-n5x

patterns:
*/fyi-android-swarming-n5x/media.android.tough_video_cases_tbmv2/*
to
*/fyi-android-swarming-n5x/media.mobile/*

etc.

I also did

*/*/media.desktop/seek_time_0_5_avg
to
*/*/media.desktop/pipeline_seek_time_0_5_avg

etc. for seek_time_9 and media.mobile per https://chromium-review.googlesource.com/c/catapult/+/713753 
Status: Verified (was: Fixed)
Looks like the migration worked.

Sign in to add a comment