New issue
Advanced search Search tips

Issue 648161 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

35.3% regression in v8.browsing_desktop at 419202:419235

Project Member Reported by ulan@google.com, Sep 19 2016

Issue description

See the link to graphs below.
 

Comment 1 by ulan@google.com, Sep 19 2016

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

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


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

chromium-rel-mac10
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 19 2016

Labels: Hotlist-Google
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 19 2016

Cc: tommycli@chromium.org
Owner: tommycli@chromium.org

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

Hi tommycli@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Plugin Power Saver Tiny: Fix Field Trial testing config
Author  : tommycli
Commit description:
  
Previously the field trial testing was incorrect. The key was the
feature name instead of the Finch experiment name.

BUG=608886

Review-Url: https://codereview.chromium.org/2342893003
Cr-Commit-Position: refs/heads/master@{#419208}
Commit  : 921187511a6fba333a6518857d697439505946d9
Date    : Fri Sep 16 17:50:59 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@419201  354.588  22.4381  5  good
chromium@419206  351.763  14.8588  7  good
chromium@419207  365.917  22.2703  8  good
chromium@419208  412.914  22.6999  5  bad    <--
chromium@419210  421.685  30.9771  4  bad
chromium@419218  413.317  7.85199  5  bad
chromium@419235  404.612  21.0778  7  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 648161

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_desktop
Test Metric: v8-gc-incremental-step_sum/v8-gc-incremental-step_sum
Relative Change: 12.53%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2387
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001105607399816288


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

| 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!
Status: WontFix (was: Assigned)
These have gone up, and then down again, and up again, on the graph, so I don't think this is related to the field trial config change.

Sign in to add a comment