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

Issue 631146 link

Starred by 2 users
Status: Fixed
Owner:
charliea@chromium.org
Closed: Aug 2016
Cc:
█ nednguyen@chromium.org
█ alexandermont@chromium.org
sullivan@chromium.org
█ rnep...@chromium.org
█ aschulman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug

Blocked on:
issue 631200


Sign in to add a comment

Reduce the number of benchmarks that power perf bots have to run

Project Member Reported by charliea@chromium.org, Jul 25 2016 
For the Windows Dell bot, we used to only be running stories that started with a "b" or "B" to reduce our (very long cycle times). These cycle times are handled by other bots by sharding tests among multiple identical machines, which we don't have quite yet for the power bots.

Until that time, and because the main focus of these bots is to catch power regressions for the time being, we should only run tests that start with a "b" or "B".

Comment 1 by charliea@chromium.org, Jul 25 2016

Cc: sullivan@chromium.org
Annie pointed that we should really do this by having a whitelist for these "fast cycle time power perf bots". In order to qualify for the whitelist, the bots must have had at least one green run that can be an indicator to use that the hardware is viable for the perf waterfall and that, if we order a couple more pieces of the same hardware, we can actually have a green bot on the waterfall.

Given that this is already true for "Mac Power Dual-GPU Perf" and "Mac Power Low-End Perf", these two are ready for the whitelist now. Unfortunately, we've never had an all green run for "Win Power High-DPI Perf" (our old Dell bot), and we'll want one before we go ahead and add it to the whitelist.

Comment 2 by charliea@chromium.org, Jul 25 2016

Summary: Reduce the number of benchmarks that power perf bots have to run (was: Power perf bots are running all benchmarks, not just those that start with a "b" or "B")

Comment 3 by charliea@chromium.org, Jul 25 2016

Blockedon: 631200
Project Member

Comment 4 by bugdroid1@chromium.org, Jul 26 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/eee42216a1c1ce1cf66cf6c224e702f0ac1e7277

commit eee42216a1c1ce1cf66cf6c224e702f0ac1e7277
Author: catapult-deps-roller <catapult-deps-roller@chromium.org>
Date: Tue Jul 26 18:41:00 2016

Roll src/third_party/catapult/ 5eeaae06d..892d222cd (4 commits).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/5eeaae06dc16..892d222cd7ed

$ git log 5eeaae06d..892d222cd --date=short --no-merges --format='%ad %ae %s'

BUG= 630278 , 631146 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2188483002
Cr-Commit-Position: refs/heads/master@{#407863}

[modify] https://crrev.com/eee42216a1c1ce1cf66cf6c224e702f0ac1e7277/DEPS

Comment 5 by charliea@chromium.org, Aug 19 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment