Revamp chromium.perf Waterfall Devices |
|||||||
Issue descriptionWe want to reduce the overhead and maintenance of our current perf waterfall (https://uberchromegw.corp.google.com/i/chromium.perf/waterfall) At a high level we are trying to increase benchmark stability and coverage (https://docs.google.com/document/d/1osarz-m5P6b_tqySx57rkqM8ku51F78ZKxKDDwZTjfU/edit#heading=h.d6ctr5b8bodz) and this is a high level goal in that space. ⛆ |
|
|
,
Aug 23 2017
,
Jul 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/tools/build/+/3036a6b10657596f608ae8f6c036f8fa4a7cedb9 commit 3036a6b10657596f608ae8f6c036f8fa4a7cedb9 Author: Emily Hanley <eyaich@google.com> Date: Thu Jul 12 12:56:32 2018 Renaming nexus5x and win10 to algin with new perf naming scheme. Nexus5x and win 10 are configurations that will be stayign the same with the 12 devices work so we thought we would get the naming out of the way now. Bug:758326 Change-Id: I8c6d03e8084572d216173b6ceceef294cadc9682 Reviewed-on: https://chromium-review.googlesource.com/1131227 Reviewed-by: Ned Nguyen <nednguyen@google.com> Reviewed-by: David Tu <dtu@chromium.org> Commit-Queue: Emily Hanley <eyaich@chromium.org> [modify] https://crrev.com/3036a6b10657596f608ae8f6c036f8fa4a7cedb9/masters/master.chromium.perf/slaves.cfg [modify] https://crrev.com/3036a6b10657596f608ae8f6c036f8fa4a7cedb9/scripts/slave/recipe_modules/chromium_tests/chromium_perf.py [modify] https://crrev.com/3036a6b10657596f608ae8f6c036f8fa4a7cedb9/masters/master.chromium.perf/master.cfg
,
Jul 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/896ba71bc975b53346521228a32536296ea5d80e commit 896ba71bc975b53346521228a32536296ea5d80e Author: Emily Hanley <eyaich@google.com> Date: Thu Jul 12 12:55:32 2018 Updating names for job triggers on nexus5x and win 10 perf Dependent on crrev.com/c/1131227 NOTRY=True Bug: 758326 Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi Change-Id: Icd5c18a166e815be5c2570cafd511bae4c545975 Reviewed-on: https://chromium-review.googlesource.com/1131230 Commit-Queue: Emily Hanley <eyaich@chromium.org> Reviewed-by: Ned Nguyen <nednguyen@google.com> Reviewed-by: Nodir Turakulov <nodir@chromium.org> Cr-Commit-Position: refs/heads/master@{#574542} [modify] https://crrev.com/896ba71bc975b53346521228a32536296ea5d80e/infra/config/global/luci-milo-dev.cfg [modify] https://crrev.com/896ba71bc975b53346521228a32536296ea5d80e/infra/config/global/luci-milo.cfg [modify] https://crrev.com/896ba71bc975b53346521228a32536296ea5d80e/testing/buildbot/chromium.perf.json [modify] https://crrev.com/896ba71bc975b53346521228a32536296ea5d80e/tools/perf/core/perf_data_generator.py
,
Jul 12
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/master-manager/+/75facbf932ba11917e9ff8973feb4f9765fd6d20 commit 75facbf932ba11917e9ff8973feb4f9765fd6d20 Author: Emily Hanley <eyaich@google.com> Date: Thu Jul 12 13:01:08 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Oct 5
|
||||
►
Sign in to add a comment |
|||||||
Comment 1 by eyaich@chromium.org
, Aug 23 2017