Better error messages for try jobs with invalid benchmark names. |
|||||||||
Issue descriptionI sent some try-jobs with an invalid benchmark. ./tools/perf/run_benchmark.py try mac-10-10 tough_canvas_cases. It turns out that the benchmark is actually called smoothness.tough_canvas_cases. The build failed with no error message, which left me pretty confused. https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2011/steps/Performance%20Test%20%28With%20Patch%29%201%20of%201/logs/stdio
,
Mar 9 2016
,
Mar 9 2016
,
Feb 3 2017
,
Feb 6 2017
Sending to correct component.
,
Apr 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 16 2018
This will be obsolete with pinpoint try, I believe
,
Jan 16
,
Jan 16
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by sullivan@chromium.org
, Mar 2 2016Cc: pras...@chromium.org nednguyen@chromium.org
Components: Tests>AutoBisect