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

Issue 642074 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Strange behavior with git cl try <perf bisect bot>

Project Member Reported by csharrison@chromium.org, Aug 29 2016

Issue description

I have a CL implementing a loading optimization:
https://codereview.chromium.org/2282303002/

I used git cl try to run some perf bisects using run-perf-test.cfg

Here is one of them:
https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/855

I talked with sullivan@ who said that the job was strangely producing no measurements, when I asked how to measure the change's impact.

Was I holding it wrong? The command I used to spin up the bisects was:
git cl try -b mac_hdd_perf_bisect -b mac_10_10_perf_bisect -b mac_10_11_perf_bisect -b mac_perf_bisect_builder -b mac_retina_perf_bisect -b win_perf_bisect -b win_perf_bisect_builder

 
Cc: pras...@chromium.org
Status: WontFix (was: Untriaged)
Ah, sorry, looks like the problem is `git cl try`. Because of the additional configuration required for a perf tryjob, you should use `tools/perf/run_benchmark try` as documented here: https://www.chromium.org/developers/telemetry/performance-try-bots
Components: Speed>Bisection

Sign in to add a comment