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

Issue 593492 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Feature



Sign in to add a comment

Provide a way to run all perf tests in a perf try job.

Project Member Reported by qyears...@chromium.org, Mar 9 2016

Issue description

Currently, perf try jobs where specific tests are run can be started for Telemetry tests using run_benchmark, and perf try jobs will be run on the CQ when a CL includes changes to a benchmark. However, sometimes someone might suspect that a patch has performance consequences, but is uncertain which benchmarks or metrics it might affect.

Annie, Ned, is there a way to do this now? Is this something we'd like to add in the future?

Note: This is related to an older feature request:  issue 324814 .
 
Cc: nduca@chromium.org
Our current thought is that we want to finish implementation of the system health benchmarks, which will give a clearer picture of whether Chrome overall has regressed, and then add support for running that set on the perf trybots.
I suspect that the cycle time it takes to run all perf tests gonna be too high for perf tryjobs. We should wait for system health benchmarks and only run those.
Labels: triaged
Status: Untriaged (was: Unconfirmed)
Components: Speed>Bisection
Components: Test>Telemetry
Components: -Tests>Telemetry

Sign in to add a comment