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

Issue 672958 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4.2% regression in thread_times.key_idle_power_cases at 437076:437106

Project Member Reported by majidvp@google.com, Dec 9 2016

Issue description

See the link to graphs below.
 

Comment 1 by majidvp@google.com, Dec 9 2016

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=672958

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg19TkrgoM


Bot(s) for this bug's original alert(s):

android-one
Cc: amp@chromium.org
Owner: amp@chromium.org

=== PERF REGRESSION ===


=== Auto-CCing suspected CL author amp@chromium.org ===

Hi amp@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Add testing config for VrShell experiment
Author  : amp
Commit description:
  
BUG=655199

Review-Url: https://codereview.chromium.org/2552883008
Cr-Commit-Position: refs/heads/master@{#437101}
Commit  : d355eb74474b4e6e0411676cc2295af054df2ace
Date    : Wed Dec 07 23:11:35 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev     N  Good?
chromium@437075  0.480917  0.0202318   9  good
chromium@437091  0.475219  0.0106044   6  good
chromium@437099  0.480951  0.00990822  6  good
chromium@437100  0.480795  0.0164651   9  good
chromium@437101  0.495662  0.0097333   6  bad    <--
chromium@437103  0.494194  0.0104295   6  bad
chromium@437106  0.494231  0.00720194  6  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 672958

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=animated.gif.html thread_times.key_idle_power_cases
Test Metric: thread_total_all_cpu_time_per_second/animated-gif.html
Relative Change: 2.77%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1868
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8993724855040275488


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6027773510942720

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Comment 4 by amp@chromium.org, Dec 12 2016

What is the action I'm supposed to take for this?

The change only added testing config for when a flag is enabled (which will later be a finch experiment). Right now it defaults to always being disabled.
Owner: ----
Status: WontFix (was: Untriaged)
Sorry for the noise! This alert is only on one device and looks to be within the noise.

Sign in to add a comment