New issue
Advanced search Search tips

Issue 657185 link

Starred by 0 users

Issue metadata

Status: WontFix
Merged: issue 651547
Owner: ----
Closed: May 2017
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug-Regression

Blocking:
issue 651547



Sign in to add a comment

57%-222.4% regression in smoothness.top_25_smooth at 420112:421670

Project Member Reported by robliao@chromium.org, Oct 18 2016

Issue description

Due to a loss in perf coverage due to a field trial configuration issue, bisect cannot identify the regressing changelist.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=657185

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


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

chromium-rel-mac-hdd
chromium-rel-win7-x64-dual
Blocking: 651547
Labels: Hotlist-Input-Dev OS-Mac OS-Windows
Project Member

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

Mergedinto: 651547
Status: Duplicate (was: Untriaged)

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


===== SUSPECTED CL(s) =====
Subject : Update fieldtrial_util To Handle Combined Fieldtrial Config Format
Author  : robliao
Commit description:
  
BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2373843002
Cr-Commit-Position: refs/heads/master@{#421670}
Commit  : 8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a
Date    : Wed Sep 28 22:51:09 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@421636  8.97425  5.22366   8  good
chromium@421666  7.053    0.251737  8  good
chromium@421668  6.791    0.37454   5  good
chromium@421669  7.036    0.382861  5  good
chromium@421670  22.9522  0.526858  5  bad    <--
chromium@421674  23.146   0.358696  5  bad
chromium@421681  22.6672  0.526846  5  bad
chromium@421695  20.9174  5.98606   8  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 657185

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: first_gesture_scroll_update_latency/https___www.google.com_calendar_
Relative Change: 93.33%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1513
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8998424630721182176


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

| 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: Available (was: Duplicate)

Comment 6 by rbyers@chromium.org, Nov 18 2016

Labels: Performance
Labels: -Performance Performance-Responsiveness
Status: WontFix (was: Available)
This looks like it's due to loss in perf data? 

Sign in to add a comment