Add presubmit script to update src side json with new/deleted benchmarks |
||||
Issue descriptionCurrently when a new benchmark is added or an old one is removed from the chromium.perf waterfall, the benchmark owner has to manually run the generate_perf_json.py script to generate the correct benchmarks on the waterfall. This should be part of a presubmit when changes happen in that directory.
,
Feb 13 2017
The recipe? This would be a presubmit script source side. It wouldn't have anything to do with recipes.
,
Feb 13 2017
As comment#0 states, right. But could we do something on the build side that does this for us per-build - or even a builder that does this with each commit to that project directory?
,
Feb 14 2017
,
Feb 15 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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 15 2018
This work is done by Ashley already |
||||
►
Sign in to add a comment |
||||
Comment 1 by benhenry@chromium.org
, Feb 13 2017Components: Speed>Benchmarks