version and stage telemetry tarball per chrome version, rather than chromeos build + version |
|||
Issue descriptionThis idea will require a design doc, but the basic sketch is: - We re-stage dep-telemetry_dep.tar.bz2 (which is inside of autotest_packages.tar artifact) for every build and board, despite the fact that it is unique per chrome version and doesn't have any board dependence. Consider pulling this out of autotest_packages.tar, and turning it into a separately staged artifact that doesn't need to be re-staged for every build+board, but only for every chrome version.
,
Jul 26 2016
+xixuan Is this something you can do after the AU work is completed?
,
Jul 26 2016
no problem, I will take a look at it after that.
,
Mar 16 2018
Bulk closing Infra>Client>ChromeOS issues untouched in over a year. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sbasi@chromium.org
, Jul 25 2016TELEMETRY_DEPS = ['dep-telemetry_dep.tar.bz2', 'dep-page_cycler_dep.tar.bz2', 'dep-chrome_test.tar.bz2', 'dep-perf_data_dep.tar.bz2'] Note that telemetry_dep gets pulled onto the DUTs do browser tests. I believe perf_data is the larger tarball which stores the web replays.