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

Issue 820504 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows
Pri: 3
Type: Bug

Blocked on:
issue 776804



Sign in to add a comment

Only fetch Telemetry's benchmark dependencies on Perf bots; delete numpy and cv2

Project Member Reported by kbr@chromium.org, Mar 9 2018

Issue description

In https://bugs.chromium.org/p/chromium/issues/detail?id=776804#c38 we identified that Telemetry's binary dependencies aren't needed any more at least for the purpose of providing the numpy and cv2 libraries, which was the original motivation for adding them.

Unfortunately, at this point Telemetry's benchmark dependencies are being fetched on *all* bots:

https://cs.chromium.org/chromium/build/scripts/slave/recipe_modules/chromium/gclient_config.py?type=cs&q=checkout_telemetry_dependencies&sq=package:chromium&l=24 .

This seems unnecessary, but I don't know whether test suites like telemetry_perf_unittests, which run on many bots and on the CQ, need these pages.

If not, then we should change this so that the Telemetry binary dependencies are fetched only on the Perf bots, and reduce the access control lists for the general Chromium bots to remove access to certain cloud storage buckets like the Telemetry partner bucket.

 
Owner: nednguyen@chromium.org
Status: Assigned (was: Untriaged)
Telemetry benchmarks need stuff like this:

Fetch dependencies for benchmark system_health.memory_desktop
tools/perf/page_sets/data/system_health_desktop_021.wprgo
tools/perf/page_sets/data/system_health_desktop_054.wprgo


I think that's only for actual perf tests, although telemetry_perf_unittests might need them. Ned would know more.
Project Member

Comment 2 by bugdroid1@chromium.org, Mar 9 2018

Status: Fixed (was: Assigned)

Sign in to add a comment